Hi Darren, Thanks for sharing this with us! This is indeed remarkable - even if we generally don't recommend adding support for another database "late" in the project.
I'm very curious about this integration, so I hope you don't mind me asking you a couple of things: - Do you use stored procedures? - Do you use built-in functions? - Did you use the @Support annotations to ensure compatibility? - How did you ensure that schemas were compatible, i.e. did you use any "special" data types? - What's the most complex SQL query you've written in this project? - Did you use any UPSERT statements, or pessimistic locking (FOR UPDATE), or INSERT .. RETURNING or anything else that jOOQ "heavily" emulates across the various SQL dialects? Anyway, it's really great news! Best Regards, Lukas 2014-03-18 21:31 GMT+01:00 Darren S <[email protected]>: > I've be developing an application for about the last four months. Its > about 40 KLOC. I've been running against mysql, h2, and hsqldb with the > intention that I'd support PostgreSQL too. I've been too lazy to setup > postgres until now. So I turned postgres, setup the schema, switch the > dialect to Postgres in jOOQ and it just worked. Seriously, not a single > issue. My full suite of automated tests all succeeded. That was pretty > impressive. > > Darren > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
