I've responded to your comments in line as well.
>From your message, I cannot tell why the `n_p_c` table has not been found. > It could be due to: > > - Lacking qualification. You've removed the schema name from the generated > SQL. Perhaps the table is in a different schema? > - Case sensitivity. Perhaps the table is not in lower case, but in upper > case? Depending on your MySQL settings and the operating system you're > using, this may or may not be relevant, in MySQL > - Wrong SQLDialect (as seen below). If this is also being executed on > HSQLDB, then setting the SQLDialect to HSQLDB will generate "n_p_c" (with > double quotes rather than backticks) > Setting the render name style to "AS_IS" fixed the issue of `n_p_c` table not being available for problem 1. Your generated code seems to indicate that a default expression exists on > the n_p_c table. But does it exist in your MySql database as well? Or did > you generate the jOOQ code from HSQLDB and the default expression exists > only there? > The JOOQ code was generated from MySQL Notice also how you're using the MySQL dialect in jOOQ (see synthetic stack > trace element at the top), but you're connecting to an HSQLDB database. > This doesn't work of course. You have to use SQLDialect.HSQLDB when > connecting to HSQLDB. Good catch on this one. I need two instances of my application running for the integration test. One of the application's dialect was not configured to HSQLDB. That's why I was seeing Problem 3 with "DUAL" table. I updated the dialect for the second instance and that problem is resolved. Thank you very much for your advice on using MySQL for the integration tests. I will look into that as a next step after discussing it w/ the bigger team. Thank you for your reply. > -- 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.
