I did do like this, but it didn't work. ----- Original Message ----- From: "Thomas Yip" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 28, 2001 11:50 AM Subject: Re: [castor-dev] Problem about delete an object and then create a same object in one transaction.
> > You can keep the deleted instance, and create it back. > > Castor JDO must be very strict about "one instance per identity per > transaction", otherwise a program might introduce inconsistence and might > introduce unexpected side effect. It is not recommended, nor supported. > > > > Thomas > > > -----Original Message----- > >From: Low Heng Sin [mailto:[EMAIL PROTECTED]] > >Sent: Tuesday, November 27, 2001 7:27 PM > >To: [EMAIL PROTECTED] > >Subject: Re: [castor-dev] Problem about delete an object and then create a > same object in one transaction. > > > >Hi, > >We run into the same issue and didn't find any workaround for that. We have > >to modify the source code to change the delete behaviour to solve the > >issue. > > > >Regards, > >Low > > > >-----Original Message----- > >From: Zhou Ye [mailto:[EMAIL PROTECTED]] > >Sent: Wednesday, November 28, 2001 11:17 > >To: [EMAIL PROTECTED] > >Subject: Re: [castor-dev] Problem about delete an object and then create > >a same object in one transaction. > > > > > >Thank you, Snyder. > > > > But if the two operations must in one transaction, do you have some way > >to avoid this problem? > > > > I also try to use long transaction, but if the second transaction > >failed, it can't undo the delete operation. > >What's wrong? > > > > > >----- Original Message ----- > >From: "Bruce Snyder" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Wednesday, November 28, 2001 4:54 AM > >Subject: Re: [castor-dev] Problem about delete an object and then create a > >same object in one transaction. > > > > > >> This one time, at band camp, Zhou Ye said: > >> > >> ZY >Tese processes are all in one transaction. > >> ZY > > >> > >> Zhou, > >> > >> This *is* the problem. Castor must remove the object from persistence > >> and it does not actually perform this step until you perform a > >> db.commit(). A solution to your problem might be to split the two > >> operations into two transactions. > >> > >> -- > >> > >> 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 > > > >----------------------------------------------------------- > >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 > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
