You can view the issue at the following URL:
<http://scarab.werken.com/issues/id/TRQ46>
Type: Enhancement
Issue Id: TRQ46
Reported by: J. Russell Smyth
drfish - ([EMAIL PROTECTED])
Details:
Summary: Alter Internal Column values to always be objects
Description: There are several places within the Torque generated code that it is
assumed that column values are objects, and can thus be null. This is not always true
in the om, but unless specified in the db sql, can often be true in the db.
My proposal is to modify torque to always store field values within the OM objects as
Java objects, and for fields that are defined as "primitive" in the schema the get/set
methods generated do the conversion from object to primitive and vice-versa.
I would also add for each primitive column an isNull()/setNull() pair, to allow even
primitive values to be nullable/checked for null.
This change would also provide a basis for the proposed addition of type conversions -
internal representation will always be the defined db->java mapping, and the generated
get/set methods will use the translation code.
Please provide feedback on this idea as it would be most usefull to me and I would be
willing to work on it if it is a change that would be benificial to all.
Status: New
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
