Issue 'TRQ46' has just been modified by user 'drfish'
You can view the issue detail at the following URL:
<http://scarab.werken.com/issues/id/TRQ46>
The following modifications were made to this issue:
>Is the work really worth it? Why not define columns that allow null values as being
>of javaType="object".
Two reasons:
1 - this is not always realistic - If I want my om to use primitive values, but my
(legacy) database does not specify "NOT NULL" then you run into a problem.
2 - primary/foreign keys. Along with the change that I am working on for TRQ41 raises
the issue of setting null keys in pk fields (there is a whole other discussion here,
but I will leave that...). I am modifying the code to return the specified values for
PK/FK fields rather than the ObjectKey derivitaves, but this opens the possiblity that
pk fields are not "object" and thus not nullable. Do you suggest that PK/FK fields
should always be objects?
Please try to keep in mind the use of Torque with existing/legacy database. With the
reverse engineering support in Torque, I cannot belive I am the only one using it so!
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
