This one time, at band camp, Al Caponi said:
AC>I'm using Castor 0.8.11 with MySQL 3.23.54a on RH Linux 6.2.
AC>
AC>I have encountered some problems with
AC>org.exolab.castor.jdo.Database.update(Object) where a new record is being
AC>created instead of an update to take place.
AC>
AC>The identity field - of the object passed to update - is not null and
AC>non-zero and after calling update(), the object instance is a new one with a
AC>new identity value.
AC>
AC>I'm not very sure how to 'zero in' on the problem and I'm at a loss to find
AC>out what can cause this.
AC>Has anyone encountered such problem and fixed it? Is there any info that I
AC>could provide to clarify? Any suggestion is welcome.
Al,
First off, you're using a version of Castor from November 2000.
This makes troubleshooting very difficult because a LOT of things
have changed in Castor since then.
Second, please post the client code and the mapping of the object
in question.
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
