First of all, JOOQ looks great. Good job. Hope it works for us. We develop a Java based app that works with SQL Server, Postgres and Oracle. We use an in-house ORM solution that generates common code that works across the databases. We don't use any DB specific features like data types, syntax, stored procedures, functions, views etc. It is essential that we have a single code base.
My questions are: 1. Can JOOQ be used to generate classes that will work across databases? I guess so long as the data mappings are common, it should. Also I see a generic Factory method that takes in a dialect which can be used instead of the generated Factory. 2. We map a CHAR(1) to a boolean. Can this be done? 3. We use a separate table to store sequence numbers for primary keys. Could we continue this with JOOQ? 4. How well does JOOQ perform? i.e are the overheads minimal? I've generated code but am struggling with telling JOOQ to use the default schema. ie not prefix the table names with the schema name. How can I do that with the Factory(connection, dialect, settings) method? Thanks for your time. - Ravi.
