I would strongly advise on doing any kind of DB related tests against the same database as in production. The project should be prepared to provide DB data easily, so each developer and CI job should have theirs own database, or even two: one for integration tests and second used by deployed application in e2e or manual tests. I wrote a little bit about this subject few days ago here (don't remember the subject though).
Regards, Witold Szczerba 2014-04-20 9:47 GMT+02:00 Brishkit <[email protected]>: > We are using JOOQ against MySQL DB for production code. For unit/integration > testing, we wanted to try out a in memory HSQLDB option. The problem we are > facing is the error 'Three part identifiers prohibited in statement'. If we > try Settings settings = new Settings().withRenderSchema(false); while > setting up the HSQLDB DSLContext, it complains with a 'table not found in > Statement' error. > > How do we work around this? Or should we use the same MySQL setup for > unit/integration tests? > > -- > 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.
