Hello Lukas, 50% are failing right now. If you could send me whatever you have > right now, I'm sure I can get the test ratio up to an "experimental" > 90% - 95% before releasing jOOQ 2.5.0. Note, if you feel uncomfortable > with GitHub pull requests, you can also just send files to the group, > here. > I have never used github before so yeah, i'm unfamiliar with the workflow and terminologies used. I was slogging through with porting the SQLite DDL to Firebird on the weekend, but i have this nagging feeling that i'm really doing this wrong due to my unfamiliarity with jOOQ internals.
Also some of the issues i encountered: 1. Firebird doesn't support "Identity" column directly. This can be simulated with "Before Insert" triggers and Generator values (a.k.a. SEQUENCES) http://www.firebirdfaq.org/faq29/ 2. SEQUENCEs are supported in firebird 2.0 onwards, but i'm not certain 3. "DROP TABLE IF EXISTS" not supported. There are work arounds, but it's a bit icky. Removed those from the script for now. 4. AFTER INSERT triggers that modify the just-inserted-records doesn't really make sense. etc. In any case, i've uploaded the files here https://dl.dropbox.com/u/22507462/jOOQ/jooq_fb2_20120820.7z Please let me know what to do next. Regards, ts. PS: How does jOOQ plan to deal with different dialects/versions within a particular database server? For example, firebird 2.x supports a lot of new constructs that were not supported by firebird 1.x. There are even differences between 2.0.x vs 2.1.x vs 2.5.x release. I don't think many people are still using firebird 1.x and 2.0.x (end-of-lifed already) these days, so the concern is more about 2.1.x (still supported) and 2.5.x (current stable release) vs 3.0 (soon to be alpha) Thanks.
