Hello Christopher, > Obviously this would not work on the Oracle version, though we do have > the same procedure.
It can work, but it isn't officially supported. Especially with Oracle, the problem is that numeric procedure parameters can only be fprmally mapped to BigDecimal, whereas other dialects allow for formally defining TINYINT, SMALLINT, INT, BIGINT numeric parameters. On the other hand, Oracle is the only database with true support for packages. > Why is the dialect hardcoded in the class at > generation time? Can't this be inferred at the time of the call so > that it could be removed from the generator? Yes it could. This is an improvement that I have been carrying around for a while: https://sourceforge.net/apps/trac/jooq/ticket/625 In early versions of jOOQ, all generated artefacts were dialect-dependent. They shouldn't be anymore. I'll see if this can be corrected soon Cheers Lukas
