Hello Bruce.
I performed the task in two different
transactions before & it works fine.
But the question is why Castor stucks?
I can understand 2 possible good behaviors that
could be: retrieve those new objects or don't retrieve them,
but why stuck the system?
If you perform same operation with direct JDBC connection,
this works fine within same transaction (new rows retrieved).
Why Castor should implement this differently?
Regards, Mark.
>This one time, at band camp, Mark Alishaev said:
>
>MA>Hello.
>MA>I'm evaluating Castor JDO about for about a week.
>MA>I've experienced the following bug (steps performed):
>MA> 1. Created few objects in the database.
>MA> 2. Retrieved previously inserted objects (in the same transaction).
>MA> As a result the program stucks (waits for some timeout).
>MA>
>MA>Is it a bug or a correct behavior?
>MA>May be I'm doing something wrong?
>
>Mark,
>
>If you're creating objects and fetching those same objects in the
>same transaction, this could be your problem. Because you've created
>the objects and not yet committed them, they're not yet persisted.
>They only exist in the cache. Split the creation and fetching into
>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
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
