If anyone is interested in having a schema which is supported in some of the most common databases along with populated data, then I have a suggestion to make,
http://chinookdatabase.codeplex.com/ Above Schema is supported for following servers, DB2 <http://www-01.ibm.com/software/data/db2/express/> EffiProz <http://effiproz.codeplex.com/> MySQL <http://www.mysql.com/> Oracle<http://www.oracle.com/technetwork/database/express-edition/overview/index.html> PostgreSQL <http://www.postgresql.org/> SQL Server <http://www.microsoft.com/sqlserver/> SQL Server Compact<http://www.microsoft.com/sqlserver/2008/en/us/compact.aspx> SQLite <http://www.sqlite.org/> Enjoy the JOOQ Generator Experience on all these database with consistent schema, for getting your hands dirty :) On Tuesday, October 15, 2013 1:34:08 PM UTC+5:30, Lukas Eder wrote: > > Hello and thanks for the feedback. > > > 2013/10/15 <[email protected] <javascript:>> > >> So, I finally decided to give JOOQ a real try! >> >> I'll use this thread to ask my (probably newbie) questions and post my >> comments. >> >> I plan on following the manual ( >> http://www.jooq.org/doc/3.2/manual-single-page/ ), at least for a while. >> >> I currently use PostgreSQL 9.1, on a Windows 7 machine. I use JOOQ 3.2.0 >> with the *jooq-codegen-maven* plugin and with PostgreSQL's *9.1-901.jdbc4 >> * driver. >> >> >> *My first comments/questions* : >> >> - The sample database schema : >> http://www.jooq.org/doc/3.2/manual-single-page/#sample-database doesn't >> work directly with PostgreSQL. I know you probably can't provide a schema >> that is compatible with all databases, but I'm just saying... It doesn't >> feel nice to start with those errors when starting... Don't forget that the >> manual (Which seems otherwise very nice!) is often the first real contact a >> developer will have with JOOQ! >> To make it work, I replaced : >> >> 1. "NUMBER" by "NUMERIC" (except "NUMBER(1)" by "BOOLEAN" or >> otherwise the code generator would use *Byte* as the type of the >> field instead of *Boolean*) >> 2. "VARCHAR2" by "VARCHAR" >> 3. Add semi-colons after each statement >> >> >> - It would be nice to provide some queries to populate this sample >> database with initial data. The code examples you give in the manual don't >> look impressive when they return nothing at all. >> > > Yes, it might be good to provide a link to a working sample SQL script for > each supported database. Or better, I would finally make the > integration-tests work with Maven and publish links to those tests (and the > contained SQL scripts) from the manual. This has been on the roadmap for a > while: > https://github.com/jOOQ/jOOQ/issues/682<https://github.com/jOOQ/jOOQ/issues/682?source=cc> > > >> - In the CRUD example, >> http://www.jooq.org/doc/3.2/manual-single-page/#jooq-for-crud , * >> FK_BOOK_AUTHOR* is used but I don't have this constant generated. I >> think it should be *BOOK__FK_BOOK_AUTHOR* ? >> > > Only the PostgreSQL generator generates key literals like this, because > the key namespace is defined per table, not per schema in PostgreSQL. > > Cheers > Lukas > -- 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/groups/opt_out.
