This one time, at band camp, tek1 said:
t>Please check the mailing list for my post entitled "Timestamp mismatch ->
t>Object links to anotherobjectnot loaded/updated/created in this transaction".
t>
t>By adding:
t>
t> <cache-type type="count-limited" capacity="100"/>
t>
t>to the mapping.xml file for each entity involved in the db.update(), I no
t>longer encountered the Timestamp mismatch. I still need to step through
t>the source in a debugger to see what exactly is going on though.
t>
t>Depending on what you're doing, another possible quick-n-dirty workaround
t>is to db.load() the object each time instead.
Thanks for reminding me! My apologies for my incorrect response.
I got confused with another bug. Bug 1107 actually depends upon and is
fixed by bug 1313 where I increased the default size of the count-limited
capacity from 30 to 100. I simply forgot to close out 1107. I've already
updated Bugzilla to reflect this.
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
