I would be willing to change the Torque Column class to use a
BigInteger or BigDecimal where appropriate. You'll have to tell me
the sizes which trigger switches from int to long to BigInteger
(matching ones for floating point would be nice as well, though more
tricky). I think that changing the getJavaNative() instance method's
return value based on column size will do the trick.
"Diethelm Guallar, Gonzalo" <[EMAIL PROTECTED]> writes:
> I have a schema where one of the columns is defined as:
>
> <column name="NUM_OPERACION" required="true"
> type="INTEGER" size="18"></column>
>
> This creates a table on SQL with the following column:
>
> NUM_OPERACION NUMBER(18) NOT NULL
>
> When torque generates the peer classes, this column is declared
> as an int:
>
> private int num_operacion;
>
> public int getNumOperacion()
> {
> return num_operacion;
> }
>
> public void setNumOperacion(int v)
> {
> if (this.num_operacion != v)
> {
> this.num_operacion = v;
> setModified(true);
> }
> }
>
> However, a Java int will not fit all values that will fit on a
> NUMBER(18). For example, a value stored as 4259430563478700 on
> the DB is stored as -173114196 on the Java int. Are there any
> workarounds for this, short of hand editing the Peer classes?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
