As I continue to play with JHipster, I've run into an issue of getting liquibase to work with my development database. Out of the box, I decided to use in-memory H2 as a dev database and MySQL in production. This seemed reasonable when I started, but I quickly discovered that if I try to add a change set to load data into my database using liquibase, it doesn't work with in-memory H2. It looks like liquibase is only going to work with more persistent databases.
I've run into several projects lately that don't use and/or refuse to use the JOIN keyword/syntax. I've had conversations in these projects to help people understand that, but I wonder why this is not more common across SQL database projects. This standard is not new, and it more easily defines the join section vs the WHERE/filter section, so it has good benefits. So far, the only reason I have heard to not use it is "we just don't tend to do that here." This makes me sad. I hope to continue evangelizing small changes like this in my projects, be it JOIN, use of functional programming, listening to IDE feedback (great static analysis checking... available before you ever even push!), etc. There are so many small things that help make software easier for everyone, I think.
Comments
Post a Comment