Hi,
if you set in yor schema-file the the defaultJavaType="object"
in the Database-Tag for example
<database name="dlshop" defaultIdMethod="native"
defaultJavaType="object" >
then you get Java-Object for all your primitive Data-Types in your schema file.
for example type="INTEGER" you get Object Integer in your om files.
If you don't want java Objects only for some fields then you can set
javaType="object" in you columns, and you get
Java objects for the colums where you set this.
Dag Landau
Russell Edens wrote:
This is a big heads up.
Those who are considering the upgrade should be aware of the significant
change to use int's instead of NumberKeys.
-----Original Message-----
From: Russell Edens [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 22, 2002 12:45 AM
To: Will Holcomb
Cc: [EMAIL PROTECTED]
Subject: [SOURCE] Issue #TRQS63 modified
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?listName=turbine-torque-
[EMAIL PROTECTED]&by=thread&from=241658
--
To unsubscribe, e-mail: <mailto:turbine-torque-dev-
[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:turbine-torque-dev-
[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
