thank you for the reply. let me clarify (i'm not an sql nerd, at all): - it is not true, that JDBCDatabase implements a generic (least common denominator, universal) generator, usable for any database having a correct jdbc driver; - one can't say, that the JDBCDatabase generated sql sentence in question (select 1 "one") is syntactically correct and db2 is bad at not accepting a well formed sql sentence (which error would be circumvented in a special db2 generator)
--- I had a simple use case, an application with some (not much) relatively complex queries (using an orm would really overcomplicate the life). I had some choices using native sql (e.g. though jpa, or something like ibatis), or some sort of dsl like querydsl or jooq. these queries utilize only jdbc-friendly things (constraint-based explicit table relations and really simple and everywhere present sql data types), so i was not suprised that all these choices worked perfectly with the db2jcc jdbc driver. (jooq is a very attractive opportunity for many reasons). --- i completely understood (and, in fact, would support) the SQLDialect.DB2 license. thanks, again. -- 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.
