Re: TEMP columns not populated by sth_to_objects in 0.96

[prev] [thread] [next] [Date index for 2004/06/09]

From: David Jack Olrik
Subject: Re: TEMP columns not populated by sth_to_objects in 0.96
Date: 21:33 on 09 Jun 2004
On Jun 9, 2004, at 19:04, Charles Bailey wrote:
> The problem is that if the data in core doesn't match that in the db, 
> it may mean that the object in core is being updated (but the update 
> hasn't been committed yet), in which case you don't want to overwrite 
> the update with what's in the db.

I disagree, if you fetch the object again, you want a fresh copy of the 
object. If you do not want a fresh copy, changes are that something is 
wrong with the structure of your code i.e. you should have commited 
before fetching from the db again.

        -- 
        Best regards,
David Jack Olrik <david@xxxxx.xx>             http://david.olrik.dk
GnuPG fingerprint C290 0A4A 0CCC CBA8 2B37 E18D 01D2 F6EF 2E61 9894
["The first rule of Perl club is  You do not talk about Perl club"]

(message missing)

TEMP columns not populated by sth_to_objects in 0.96
David Jack Olrik 08:54 on 08 Jun 2004

object caching and mod_perl
jason scott gessner 13:28 on 08 Jun 2004

Re: object caching and mod_perl
Tony Bowden 13:46 on 08 Jun 2004

Re: object caching and mod_perl
Perrin Harkins 14:02 on 08 Jun 2004

Re: object caching and mod_perl
jason scott gessner 14:11 on 08 Jun 2004

Re: TEMP columns not populated by sth_to_objects in 0.96
David Jack Olrik 21:33 on 09 Jun 2004

Re: object caching and mod_perl
Edward J. Sabol 14:52 on 08 Jun 2004

Re: object caching and mod_perl
jason scott gessner 16:31 on 11 Jun 2004

Generated at 11:34 on 01 Dec 2004 by mariachi v0.52