Hi Fabio,
I re factored the use of long transactions into short transactions. It takes a bit more code to write but I don't have these problems anymore.
cristi
At 01:17 PM 12/20/2002 -0600, you wrote:
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail toHi Cristi, I read your email, How do you solved "I ran into this mysterious problem too with all the combinations of cache settings."Thanks, FAbio --- Cristi <[EMAIL PROTECTED]> escribi�: > > Hi Bruce, > > if he is not using cache for those objects (... > cache="none") why is this > object's timestamp still compared to the timestamp > of the cache version > (locker) ? I ran into this mysterious problem too > with all the combinations > of cache settings. > > cristi > > At 12:21 AM 12/20/2002 +0000, you wrote: > >This one time, at band camp, Fabio Andr�s Zorzan > said: > > > >FAZ>Bruce, > >FAZ> I send you more details: > >FAZ> > >FAZ>Code of the Query and update > >FAZ>----------------------------------------------- > >FAZ> > >FAZ> oql=db.getOQLQuery("select n from > castor.Actor > >FAZ>n"); > >FAZ> results=oql.execute(); //return ~40 > Objects > >FAZ> Object o; > >FAZ> while(results.hasMoreElements()) > >FAZ> { > >FAZ> o=((Object)results.next()); > >FAZ> v.add(o); > >FAZ> } > >FAZ> > >FAZ> castor.Actor > >FAZ>actor=(castor.Actor)vector.elementAt(5);// 1 or > 2 ... > >FAZ>I have the problem > >FAZ> db.update(actor); > > > >So because you're using db.upate(), you're using > Castor's long transactions, > >correct? > > > >FAZ> <field name="creationDate" type="date" > >FAZ>required="false" direct="false" lazy="false" > >FAZ>transient="false"> > >FAZ> <sql name="creation_date" > type="date" > >FAZ>read-only="false" dirty="check" /> > >FAZ> <xml name="creationDate" > node="element" /> > >FAZ> </field> > >FAZ> <field name="updateDate" type="date" > >FAZ>required="false" direct="false" lazy="false" > >FAZ>transient="false"> > >FAZ> <sql name="update_date" type="date" > >FAZ>read-only="false" dirty="check" /> > >FAZ> <xml name="updateDate" > node="element" /> > >FAZ> </field> > > > >I'm not sure exactly why this is occurring. > However, an > >ObjectModifiedException can be thrown when a field > fails Castor's dirty > >check (which uses .equals()). This can occur when > using fields of type > >float, double, date, etc. I notice that there are > some date fields > >above. Isolate these fields by instructing Castor > not to perform its > >dirty check on them like so: > > > > <sql name="foo" type="date" dirty="ignore" /> > > > >See if the ObjectModifiedException goes away after > taking this step. > >This might then lead you down the road of locating > the actual > >problem. > > > >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 > _________________________________________________________ Do You Yahoo!? Informaci�n de Estados Unidos y Am�rica Latina, en Yahoo! Noticias. Vis�tanos en http://noticias.espanol.yahoo.com ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
