Issue TRQ46 has just been modified by user wholcomb
You can view the issue detail at the following URL:
<http://nagoya.apache.org/scarab/issues/id/TRQ46>
The following modifications were made to this issue:
I submitted a patch (TRQS63) that adds a boolean[] for each column tracking if that
column has been set or not. I did it because I had a table with null foreign keys and
the 0 going in was throwing things off. When the criteria is built there is simply a
boolean check around each add that prevents an unset value from going in.
<br /><br />
This has the disadvantage of storing the details of a member in two places, but has
the advantage of maintaining the methods that use int's (and using them internally)
rather than having the overhead of wrapping and unwrapping everything from Integers
(or whatever).
<br /><br />
It fixes my problem with foreign keys on initial insertion, but does not allow me to
make a field null once it is set. As it is, the checks in buildCriteria just skip
adding a field if it is not set, they do not enter a null value.
--
To unsubscribe, e-mail: <mailto:turbine-torque-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-torque-dev-help@;jakarta.apache.org>
