This one time, at band camp, Mark Alishaev said:
MA>Hello Bruce.
MA>I performed the task in two different
MA>transactions before & it works fine.
MA>But the question is why Castor stucks?
MA>I can understand 2 possible good behaviors that
MA>could be: retrieve those new objects or don't retrieve them,
MA>but why stuck the system?
MA>If you perform same operation with direct JDBC connection,
MA>this works fine within same transaction (new rows retrieved).
MA>Why Castor should implement this differently?
MA>
Mark,
You really answered your own question here. Just like I said before,
because you've created the objects using Castor, but you have not
yet committed them using Castor, the objects only exist in Castor's
cache. The objects will not be persisted until you perform a
db.commit() on them via Castor.
With JDBC, anything you do is immediately persisted. There is no
object caching mechanism involved.
MA>>If you're creating objects and fetching those same objects in the
MA>>same transaction, this could be your problem. Because you've created
MA>>the objects and not yet committed them, they're not yet persisted.
MA>>They only exist in the cache. Split the creation and fetching into
MA>>two separate transactions and see if that changes the results.
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
