News for hackers. Stuff that matters.
Re:How Hibernate Almost Ruined My Career by guelo on Thursday February 16, 2017 @08:16PM (#13665137)
Doesn't seem like that common of a problem to have to ship code that has to work with different databases. But if I ever had to do such a thing I would just stick with ANSI SQL.
Re:How Hibernate Almost Ruined My Career by koolba on Thursday February 16, 2017 @08:22PM (#13665163)
There's no such thing as ANSI SQL for real world applications on real world databases. Even something as simple as limiting the number of rows returned varies widely (TOP vs LIMIT vs rownum).

The correct answer is to forget about database independence and double down on just one[1] so you can use it to its full potential.

[1]: And obviously it should be Postgres...

Re:How Hibernate Almost Ruined My Career by xxs on Thursday February 16, 2017 @08:46PM (#13665269)
and you missed "fetch first" which is the ANSI thing
Re:How Hibernate Almost Ruined My Career by chii on Thursday February 16, 2017 @08:49PM (#13665283)
> common of a problem to have to ship code that has to work with different database

when you are not writing a SaaS, but shipping a piece of software for a customer to run on their own server, it's a very common use case to support different database vendors - especially in enterprise software.

Re:How Hibernate Almost Ruined My Career by flukus on Friday February 17, 2017 @12:19AM (#13666128)
Generally the database to use is dictated by the software, that or it will support one or two, not any database.
Re:How Hibernate Almost Ruined My Career by akud on Thursday February 16, 2017 @09:13PM (#13665399)
It's useful to, for instance, run your test suite against an in-memory database like sqlite or hsql, but use a "real" database in production.
Re:How Hibernate Almost Ruined My Career by RussianCow on Thursday February 16, 2017 @09:25PM (#13665459)
I think using VMs or something like Vagrant is a much better solution to that problem. You generally don't want to test against something that's drastically different than what you run in production.