Hi Kent, Great. I have created an issue and label on Github to track this: https://github.com/jOOQ/jOOQ/issues/2282
Just to be sure about where this might go: Will I be able to integration test this on a Windows 8 machine? If not Windows 8, Windows 7 maybe? Or does this run on i5/OS (or similar) only? If so, what's the best (and free) option to run this in a VM, maybe? Cheers Lukas 2013/2/27 Kent Smotherman <[email protected]> > Thanks Lukas, I was thinking that was likely the process. > > Yes, iSeries DB2 shares a core syntax and feature set with DB2, but there > are a number of differences - some of which, I won't even know until I > attempt this! So, fun for me. :) > > I'll keep the group posted here on progress. > > Thanks! > > > On Wednesday, February 27, 2013 5:19:35 AM UTC-6, Lukas Eder wrote: > >> Hi Kent, >> >> You're not missing anything obvious. Apart from the couple of hints that >> are mentioned here... >> http://www.jooq.org/community.**php <http://www.jooq.org/community.php> >> >> ... there isn't really a "standard" way of contributing support for a new >> SQL dialect. The usual approach that I chose is to: >> >> 1. Provide an implementation of jooq-meta's Database, running "plain SQL" >> through jOOQ / JDBC >> 2. Generate the information_schema / meta schema / dictionary tables, >> using that initial jooq-meta Database implementation >> 3. Re-write that jooq-meta Database implementation using the previously >> generated classes >> >> While step 3 isn't required (see SQLite integration, for instance), I see >> it as a proof of concept within jOOQ: to extensively use the jOOQ API in >> jOOQ-meta as well. >> >> Once the above is established, the real hard work starts: Making all the >> integration tests run for the new database. Is iSeries DB2 much different >> from the "standard DB2" when it comes to SQL syntax / function support? >> >> Tell me, if you need more information. >> >> 2013/2/26 <[email protected]> >> >>> I've perused the source, and have poked through a lot of messages here, >>> but I still am quite lost in trying to figure out how to start doing an >>> implementation for iSeries DB2. The fairly terse text on the site seems to >>> imply that I can use the code generator to help with some of this, and the >>> sample DB2 implementation I see also is full of auto-generated code. >>> However, how can generate code if I don't have an implementation that >>> understands the schema etc for iSeries, since it is greatly different than >>> standard DB2? >>> >>> Forgive me if I am just overlooking something obvious! >>> >>> Kent Smotherman >>> >>> -- >>> 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 jooq-user+...@**googlegroups.com. >>> >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> >> -- > 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. > > > -- 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.
