Issue TRQS63 has just been modified by user russelle
You can view the issue detail at the following URL:
<http://scarab.werken.com/scarab/issues/id/TRQS63>
The following modifications were made to this issue:
I like the removal of the ObjectKeys in favor of java types...but why change objects
to primitive types? Specifically IntegerKey's to int's? Why not make them Integer's
instead?
John's workaround may downgrade this from critical. But this seems like a workaround
to a fundamental issue. An int does not represent null value without some special
values . This change was a huge headache for us ... so much so we had to bail on RC1.
Most of the issues were related to updates and inserts for foreign keys. We do a
fair amount of narrow updates using the doUpdate(Criteria, Criteria) methods. The
other issue we ran into is the additional coercion into an ObjectKey for int column
key values. This could be change to Object if the key type become Integer. We would
really like to see object types for keys by default. Then the workaround to use
primitives could still be used for the minority of people that would want it to work
that way. I especially don't like having to compare against 0 for an int to see if it
is null. (Not to mention that some databases will have keys with a value of 0 in
them.) Because we use integers as keys for most of our tables this issue must be
raised. I don't see why most everyone who takes the 3.0 release will have similar
issues and problems.
Reference Thread:
http://archives.apache.org/eyebrowse/BrowseList?[EMAIL PROTECTED]&by=thread&from=241658
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
