Hello Sergey, Thanks a lot for your feedback!
> 1. renames PROJCODE_DEV1 to PROJCODE ( in runtime we use schema mapping and > map this name to PROJCODE_<schema_suffix>) So a schema re-writing functionality is really a nice feature for many of you. Let's raise the priority on this, then: https://sourceforge.net/apps/trac/jooq/ticket/958 > 2. changes data type of one column from java.sql.Date to > java.sql.Timestamp. > By default, jooq maps Oracle DATE type to java.sql.Date. > java.sql.Date doesn't contain time, but Oracle DATE type contains seconds. > So we have to change type of field in generated record, parameter in > procedure etc. (Fortunately, one column only :) > This problem is related to > http://groups.google.com/group/jooq-user/browse_thread/thread/4ad607718d4e9533 > (no custom type mapping) Yes, the custom type mapping will be handy for various use cases. I'm aware of this problem. I'll start a new thread about this topic to find out what you guys really need. In this case, though, beware of weird performance impacts when binding timestamp instead of date: http://stackoverflow.com/questions/6612679/non-negligible-execution-plan-difference-with-oracle-when-using-jdbc-timestamp-o > 3. changes type of sequences from BigInteger to long. Most of primary keys > in our schema are NUMERIC(18,0) and jOOQ generates long type for them. I > thought that may be possible consider sequence's MAXVALUE for defining type. > For example, if we declare sequence with MAXVALUE 999999999999999999 (18 > digits) then Long type will be selected, otherwise - BigInteger. That's a nice improvement. In jOOQ 2.0, I have already introduced a generic type parameter to org.jooq.Sequence<T extends Number>. I wasn't aware of the MAXVALUE field in Oracle, though. I'll file this as a feature request: https://sourceforge.net/apps/trac/jooq/ticket/961 Cheers Lukas
