Greetings Werner and Ralf,
I will not be writing an issue report for Castor's Bugzilla
regarding the unknown type error with MySQL 5.0.
During my investigation, I have determined that the problem has
nothing to do with Castor, but rather is isolated to a fault with part of
the way I was trying to use MySQL's Connector/J. I want to thank you for the
time and effort you expended on helping me.
On an unrelated note, you might want to review
org.exolab.castor.persist.ClassMolder, line 1102. The If-statement written
there seems to check if variable o1 is instanceof java.math.BigDecimal and
then calls ol.compareTo(o2) to check for equivalence (with o2 as an instance
of the Object class). However, recent versions of Sun's Java do not seem to
implement the compareTo method of BigDecimal to check against Object types.
Perhaps checking o2 for an instance of BigDecimal and a subsequent casting
would work?
Keep up the great work!
Michael Stabler
Software Engineer
[EMAIL PROTECTED]
202.863.3580
www.cssiinc.com
-----Original Message-----
From: Michael Stabler [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 12, 2005 10:02 AM
To: '[email protected]'
Subject: RE: [castor-user] Problems with OQLQuery result set using MySQL
5.X?
Hello Werner,
Thank you for the speedy reply...
>> it's a long time since I've been exposed to 'greetings'
We old fogeys can't help it. There's no school like old school. ;)
1) Where can I obtain Connector/J 4.1.X?
2) I can switch between MySQL 4.X Connector/J 3.0.X configuration
and a MySQL 5.X Connector/J 3.1.7 configuration. I need your brain-power
focusing on what I can not do - figuring out the big picture. I'll worry
about the easy stuff - like reverting back to a 4.X/3.0.X environment. If
you'd like me to do more testing in either 4.X or 5.X just let me know.
You're going to have to handle the hard stuff for us.
Sincerely,
Michael.
Michael Stabler
Software Engineer
[EMAIL PROTECTED]
202.863.3580
www.cssiinc.com
