RE: Re[4]: [ZODB-Dev] know the state of an object

2005-10-20 Thread Tim Peters
[Victor Safronovich] >>> invalidate [Dieter Maurer] >> I think, this is not easily available, but >> "obj._p_changed = None" might work [Victor] > What about obj._p_invalidate()? I don't think _p_invalidate() existed before ZODB 3.3. At and after 3.3, obj._p_invalidate() is the

Re[4]: [ZODB-Dev] know the state of an object

2005-10-19 Thread Victor Safronovich
Hello Dieter Maurer, Thursday, October 20, 2005, 1:53:35 AM, you wrote: DM> Victor Safronovich wrote at 2005-10-18 13:18 +0600: >> ... >> May be usefull to add some simple workflow to Persistent class with >> states: >> GHOST >> UPTODATE >> CHANGED >> STICKY >> trans

Re: Re[2]: [ZODB-Dev] know the state of an object

2005-10-19 Thread Dieter Maurer
Victor Safronovich wrote at 2005-10-18 13:18 +0600: > ... > May be usefull to add some simple workflow to Persistent class with > states: > GHOST > UPTODATE > CHANGED > STICKY > transitions: Most of the transitions are there (though through strange names) > acti

Re[2]: [ZODB-Dev] know the state of an object

2005-10-18 Thread Victor Safronovich
Hello Jim Fulton, Friday, October 14, 2005, 7:01:00 PM, you wrote: JF> The long term solution to these are other related use cases is to start JF> using events in ZODB. That is, ZODB should use zope.event to report JF> happenings of potential interest to applications. Then applications JF> can

RE: [ZODB-Dev] know the state of an object

2005-10-14 Thread Tim Peters
[Chris Withers, about getting at the collection of modified objects] > How hard would it be to expose? The coding would be trivial in ZODB 3.6 (earliest version a new feature could land) if limited solely to Connection objects. More work to specify the interface and write tests. > Would there be

RE: [ZODB-Dev] know the state of an object

2005-10-14 Thread dvd
On Thu, 2005-10-13 at 19:04 -0400, Tim Peters wrote: > > from the connection object, > > You didn't say which version of ZODB you're using. Since you believe a > Connection keeps track of which objects have been modified, I'll assume > you're using ZODB 3.3 or later (which is either true, or you

Re: [ZODB-Dev] know the state of an object

2005-10-14 Thread Jim Fulton
Tim Peters wrote: [dvd] ... So, in the end, I don't see any hope for you via this route, short of this: register an object as changed in your __setattr__ without worrying at all about _why_ __setattr__ was called. Later, when you "do something" with your list of modified objects, simply ignore

Re: [ZODB-Dev] know the state of an object

2005-10-14 Thread Chris Withers
Tim Peters wrote: I'm developing a ZODB based Collection Management software, and, for a bunch of reasons, i have to know the list of modified objects before the current transaction commit. Looking around seems there is no a public API to obtains this list That's true. How hard would it be t

RE: [ZODB-Dev] know the state of an object

2005-10-13 Thread Tim Peters
[dvd] > this my first post to this list, and first of all thanks for your work. > > I'm developing a ZODB based Collection Management software, and, for a > bunch of reasons, i have to know the list of modified objects before the > current transaction commit. Looking around seems there is no a publ

[ZODB-Dev] know the state of an object

2005-10-13 Thread dvd
Hi all, this my first post to this list, and first of all thanks for your work. I'm developing a ZODB based Collection Management software, and, for a bunch of reasons, i have to know the list of modified objects before the current transaction commit. Looking around seems there is no a public API