> Especially with
> Oracle, the problem is that numeric procedure parameters can only be
> formally mapped to BigDecimal, whereas other dialects allow for
> formally defining TINYINT, SMALLINT, INT, BIGINT numeric parameters.
Oracle:
public static final org.jooq.Parameter<java.math.BigDecimal> OBJID =
createParameter("OBJID", org.jooq.impl.SQLDataType.NUMERIC);
SQLServer:
public static final org.jooq.Parameter<java.lang.Long> ObjID =
createParameter("objID", org.jooq.impl.SQLDataType.BIGINT);
If the parameter fits in a Long (it is the case since our 2 schemas
work the same and SQLServer uses a long), what would happen if I use
the SQLServer generated model on the Oracle DB? Is there some
conversion or it would just fail saying that "BIGINT" is not
applicable for Oracle?
On a related topic, if a field is Boolean (BIT) on SQLServer but a
Byte (TINYINT) on Oracle (with values 0=false, 1=true), would the
SQLServer model work on an Oracle DB with some sort of automatic
conversion (e.g.: from 1 to TRUE)?
> 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
Thanks!
-Christopher
