> Let's see how this can be solved... Hmm, looks like org.jooq.Sequence needs a generic type parameter <T>, and then maybe there is need for a code-generation configuration parameter for backwards compatibility where the generated sequences can be forced to bind <T> to BigInteger, regardless of the RDBMS' specification...
This seems more proper anyway, since I actually don't know if there exist RDBMS with VARCHAR sequences...? I think this change can be introduced in a minor release: - BigInteger can be enforced for backwards compatibility - The lacking generic type will cause rawtype warnings, which is OK
