RE: __no_side_effects__, was Re: [ZODB-Dev] Re: [Zodb-checkins] SVN:ZODB/branches/3.4/

2005-04-28 Thread Tim Peters
[Tim Peters] >> What I seem to be missing entirely here is why Zope ships Prefix >> instances at the base ZEO msg level to begin with; maybe it's to call >> some method I misunderstand (or haven't even bumped into yet <0.6 >> wink>). [Shane Hathaway] > When you want to undo something, Zope asks th

Re: [ZODB-Dev] ZODB 3.2.8 final released

2005-04-28 Thread Paul Winkler
On Thu, Apr 28, 2005 at 02:45:52PM -0400, Tim Peters wrote: > Excellent! Thank you for trying it. Note that your older server still > contains the older implementation of Prefix, so its comparison function > makes no use of the .path attribute your newer client creates; i.e., with > the combo, y

Re: __no_side_effects__, was Re: [ZODB-Dev] Re: [Zodb-checkins] SVN: ZODB/branches/3.4/

2005-04-28 Thread Shane Hathaway
Tim Peters wrote: > What I seem to be missing entirely here is why Zope ships Prefix instances > at the base ZEO msg level to begin with; maybe it's to call some method I > misunderstand (or haven't even bumped into yet <0.6 wink>). When you want to undo something, Zope asks the ZEO server for a l

RE: __no_side_effects__, was Re: [ZODB-Dev] Re: [Zodb-checkins] SVN: ZODB/branches/3.4/

2005-04-28 Thread Tim Peters
[blast from the past -- April 15] [Tim Peters] >> ... I'd reserve intense dislike for, e.g., __no_side_effects__ >> (remember that one?). [Paul Winkler] > Yes, I found it recently when I fixed a bug in ZopeUndo/Prefix.py. Does > anything actually rely on that attribute, and what for? The only ch

RE: [ZODB-Dev] ZODB 3.2.8 final released

2005-04-28 Thread Tim Peters
[Tim Peters] >> ... >> You might want to try that (by temporarily installing ZODB 3.2.8 on >> a client) to verify that your scenario does in fact work for you now. [Paul Winkler] > I just downloaded 3.2.8 and copied Prefix.py into my Zope 2.7.6-b2 > installation. Seems to work fine! Excellent! T

Re: [ZODB-Dev] ZODB 3.2.8 final released

2005-04-28 Thread Paul Winkler
On Thu, Apr 28, 2005 at 02:00:49PM -0400, Tim Peters wrote: > "his" combo with a preliminary patch. You might want to try that (by > temporarily installing ZODB 3.2.8 on a client) to verify that your scenario > does in fact work for you now. I just downloaded 3.2.8 and copied Prefix.py into my Zo

RE: [ZODB-Dev] ZODB 3.2.8 final released

2005-04-28 Thread Tim Peters
[Tim Peters] >> Neither did I, Paul -- I don't know ZopeUndo from a hole in the ground. >> It _might_ have helped if you had added an entry to ZODB's news file >> recording that ZopeUndo.Prefix had changed. >> ... [Paul Winkler] > Yeah, but I don't know ZODB's news file from shinola ;-) I've never

[ZODB-Dev] Cache hints

2005-04-28 Thread Rajeev J Sebastian
Hello, Is there any way to forcibly remove something from the cache on client-side (when using Zeo) ? And, conversely, is there anyway to always keep something in the cache, between restarts of my PyQt application ? I think its called a persistent cache ? Rajeev J Sebastian _

Re: [ZODB-Dev] Invalidations

2005-04-28 Thread Jim Fulton
Rajeev J Sebastian wrote: ... What I also need, is a way to know which objects have changed, without having to maintain copies: the reason is to show those changes to the user in my (long-running) PyQt window. As I mentioned before, ZODB doesn't provide a mechanism for this. I would like it to fo

Re: [ZODB-Dev] Invalidations

2005-04-28 Thread Rajeev J Sebastian
> I assume Rajeev doesn't really want to call sync() automatically, because > that's never what anyone asking that question really wants. What they > invariably _want_ is for ZEO to process invalidations by magic, and they've > been calling sync() manually as a way to get that to happen. What I

[ZODB-Dev] Undo, undo, undo, undo and then commit doesn't work

2005-04-28 Thread Stefan Milenkovic
Hello, I have written a script for undoing some transactions in a database. The problem is that for each transaction I want to undo, I have to add a new one (because of the commit for undoing) and it is very slow. Moreover, the size of the database grows quickly, which is a bad point. I have trie