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:
On the having to specify javaType="object"...
Even if you made this required for fields that may be null, which seems like putting a
burden on the developer that torque could pretty easily take care of, this still does
not deal with the issue where someone may mistakenly forget to initialize a field and
torque will put in a 0 rather than complaining.
I personally occassionally make programming errors and I try to write my code to
complain rather than having an unintentional side effect when this happens. I am using
some of my torque stuff in webapps and it is handy to be able to check if a field has
been set yet. At the very least it is good if it doesn't just make values up if I
forget to set them.
--
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>
