Hi Bruce, Sorry for the late reply, but it is better late than never ;). In the attached zip you can find a test case that reproduces the problem.
The archive contains a test case of another problem that I've recently discovered. This is a problem with reference handling - when an object has list of references (e.g. of A class) as well as a single reference to the same A class. And when the single reference is set to point to a different A instance the list of references is reduced by one. Sorry for the cumbersome explanation - it is better to see a concrete example. The attached tables.sql contains database schema as well as sample data. Environment: - MsSql server 7.0. - j-netdirect JDBC driver - Java 1.3 - JBuilder 6 Thanks, Alex -----Original Message----- From: Bruce Snyder [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 06, 2002 2:37 AM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] Bug #963 This one time, at band camp, Alex Grivnin said: AG> There is a fix in ClassMolder from Mickael Guessant (version 9.4, line 627) that causes stack overflow when storing objects that have references to each other and are not dependent. AG> AG> I do not know what is the solution, but after I removed the fix, it worked ok for me. Alex, The JDO tests do not exhibit any failures due to this patch and there are plenty of relations in the tests that are not dependent. Can you provide a small test case that demonstrates this behavior? Bruce -- perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&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 ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
