Tag: database

  • Book Review: Beginning Hibernate by Jeff Linwood, Dave Minter

    Book Review: Beginning Hibernate by Jeff Linwood, Dave Minter

    Sweet introduction to Hibernate. I can’t believe it doesn’t cover migrations (and I’m sure some people will point out migrations it’s not part of Hibernate, but without it, there’s no good way to maintain a production database). The book is on the short side for a computer book and that’s a huge plus. Even then, […]

  • Setting (database) credentials on a Spring Boot project, the right way

    Setting (database) credentials on a Spring Boot project, the right way

    Searching online for how to set up the credentials to access the database (or any other service) while in development leads to a lot of articles that propose something that works, but it’s wrong: putting your credentials in the application.properties file that you then commit to the repository. The source code repository should not have […]

  • How to use Lobos with Heroku

    Lobos is a Clojure library to create and alter tables which also supports migrations similar to what Rails can do. I like where Lobos is going but it’s a work in progress, so the information here might be out of date soon, beware! Let’s imagine a project called px (for Project X of course) with […]

  • Generating sample data

    As I’ve said in previous posts, I like being able to generate sample data for the projects I’m working on very quickly. It allows new developers to get up to speed fast, and new developers to move faster. When I don’t have a sample data generation method, I’m always scare to try whether, for example, […]

  • Deleting all records in a Rails project

    During the initial phase of development of a Rails application I don’t use migrations as migrations but as table definitions. Until I deploy I feel free to modify the migration files as much as I want and I have one per table. The downside of that is that the only way to apply the changes […]

  • Really resetting the database

    When I start coding a Ruby on Rails project, I find myself modifying the migration files over and over. I know this is not the way they were intended to use, but to avoid upfront design, I only ad fields when I need them. If I respected the way migrations were intended I would end […]