if your use cases allow it.
Gary
>
> Erik
>
>
>
> 2011/7/29 Gary Poster :
>>
>> On Jul 28, 2011, at 6:38 PM, Erik Allik wrote:
>>
>>> Gary, since you're the author of zc.twist (as I understand), I take
>>> this as an exhaustive answer, and t
me.sleep() to give some breathing room
probably would have been fine, with hindsight, and much simpler. The use of
Twisted is a very questionable convenience, and the way zc.async uses Twisted
is not to be copied 99% or more of the time.
Gary
>
> Thanks again and best regards,
&g
Hello Erik. As the author, I'll suggest that you move on to a ZODB connection
pool used by the usual Twisted-provided thread pool. zc.twist is maybe
interesting and maybe clever, but of very limited usefulness. I suspect it is
only used in zc.async, and that's probably as it should be. It's
On Dec 7, 2009, at 11:08 AM, Erik Dahl wrote:
...
> Our slow loading object was a persistent with a regular list inside of
> the main pickle. Objects that the list pointed to were persistent
> which I believe means that hey will load separately. In general we
> have tried to make our per
I'm the primary zc.catalog author.
He is running read-only, so savepoints shouldn't be very pertinent.
The original poster is correct that the cache is cleaned out at
transaction boundaries (or savepoints, as Alan said).
I don't have experience with running the db in readonly mode in
produ
Uh-oh, I'm implicated!
(see below)
On Jun 3, 2008, at 12:53 PM, Sean Allen wrote:
...
If you do that in gemstone, there is only one copy of Order B, no
matter
what variable in what dictionary you come at it from. And its drop
dead
simple.
I looked at implementing that with zodb an
On Mar 20, 2008, at 11:04 PM, Sean Allen wrote:
I've been playing with this and I'm still having a disconnect 3 week
later.
1. I love the zc.relation stuff it answers one area of stuff I
hadn't even gotten to yet.
cool :-)
2. I'm just totally missing something
less cool. :-/
If I h
Hi Kenneth.
First, make sure you do a transaction.begin() (or transaction.abort())
before you view your database for a given operation. This will sync
invalidations for a given transaction, even if it will only be a read
transaction, and reset the MVCC view.
The partial-view behavior you
On Mar 10, 2008, at 6:34 PM, Kenneth Miller wrote:
Hello all,
I'm currently developing my application ontop of zodb/zeo, and
the idea of having the Zeo server the only single point of failure
still bothers me. My question is, has anyone thought of any
solutions for this. My idea was t
On Feb 27, 2008, at 10:03 AM, Sean Allen wrote:
On Feb 27, 2008, at 5:33 AM, Laurence Rowe wrote:
Sean Allen wrote:
been looking for anything along those lines.
in particular, strategies and gotchas for how to store objects.
everything i've found is basically just a single type of object
On Jan 17, 2008, at 11:57 AM, Flavio Coelho wrote:
Some progress!
Apparently the combination of:
u._p_deactivate()
transaction.savepoint(True)
transaction.commit()
helped. Memory consumption keeps growing but much more slowly
(about 1/5 of the original s
On Nov 1, 2007, at 4:25 PM, Matt Hamilton wrote:
David Binger mems-exchange.org> writes:
On Nov 1, 2007, at 7:05 AM, Matt Hamilton wrote:
Ie we perhaps look at a catalog data structure
in which writes are initially done to some kind of queue then moved
to the
BTrees at a later point.
A s
On Aug 2, 2007, at 9:33 AM, Jim Fulton wrote:
On Aug 2, 2007, at 7:51 AM, Chris Withers wrote:
Gary Poster wrote:
you can call cache minimize after a threshold.. maybe every 100
iterations.
sounds good, assuming you know you are not writing.
I've used this trick loads, especiall
On Aug 1, 2007, at 4:16 PM, Alan Runyan wrote:
snip...
line 96, in
__setstate__
Persistent.__setstate__(self, state)
MemoryError
means you have run out of memory. check your jail or how much memory
you have allocated.
you can call cache minimize after a threshold.. maybe every 100
i
On Jul 19, 2007, at 6:36 PM, Tobias Rodäbel wrote:
Hi Gary,
thanks a lot for your response!
Am 19.07.2007 um 15:52 schrieb Gary Poster:
- Is this consistently reproduceable, or intermittent? Unless you
are intentionally creating a conflict in a test, any errors in the
changes in 3.9
On Jul 19, 2007, at 10:36 AM, Roger Ineichen wrote:
Hi Tobias
Auftrag von Gary Poster
Gesendet: Donnerstag, 19. Juli 2007 15:53
An: Tobias Rodäbel
[...]
zope.app.keyreference-3.5.0_dev_r77018-py2.4.egg requires
ZODB3>=3.9.0-dev-r77011
But there might be a caching problem within ZO
On Jul 19, 2007, at 7:11 AM, Tobias Rodäbel wrote:
Hi,
zope.app.keyreference-3.5.0_dev_r77018-py2.4.egg requires
ZODB3>=3.9.0-dev-r77011
But there might be a caching problem within ZODB3-3.9.0 dev r77011,
my debug session tells:
> /development/Zope3/MyProject/eggs/ZODB3-3.9.0_dev_r7701
On May 9, 2007, at 1:40 PM, Gary Poster wrote:
On May 9, 2007, at 1:35 PM, Christian Theune wrote:
Hey,
my new buildbot just discovered this:
Failure in test test32 (BTrees.tests.testBTrees.FamilyTest)
Traceback (most recent call last):
File "/usr/lib64/python2.4/unittest.py"
On May 9, 2007, at 1:35 PM, Christian Theune wrote:
Hey,
my new buildbot just discovered this:
Failure in test test32 (BTrees.tests.testBTrees.FamilyTest)
Traceback (most recent call last):
File "/usr/lib64/python2.4/unittest.py", line 260, in run
testMethod()
File "/data/buildbot/sla
Hi. ZODB does not currently work with Py2.5.
Gary
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev
I assume you are more interested in seeing if you can get someone to
raise a compelling -1 than in hearing a chorus of +1s. But FWIW, +1
in getting rid of versions. It sounds like it would simplify the
code significantly, which would be its own "feature".
Gary
On Mar 27, 2007, at 10:51 AM, Christian Theune wrote:
Thanks for the notice, I'll look into it.
Might take a while to get a FreeBSD installed as a sandbox
somewhere ...
FWIW, It smells more like a 64 bit vs. 32 bit machine/OS question,
but that's just on the basis of fly-by-diagnosis. :-
On Feb 12, 2007, at 10:01 AM, Manuel Vazquez Acosta wrote:
Hi Gary,
Although the shared buffer indeed has a queue-like interface
there's a catch for my needs. I need that pull method to retrieve
the item in the head and to move the head forward, and not to
remove the item from the buffer
On Feb 11, 2007, at 7:29 PM, Manuel Vazquez Acosta wrote:
My scenario is akin a consumer-producer with shared buffer.
Consumers pull items from the buffer whilst producers put items in
the buffer. The buffer is an OOBTree along with an IOBTree which
gives "serial" numbers to the keys of th
On Oct 5, 2006, at 9:37 AM, Jim Fulton wrote:
Russ Ferriday wrote:
Do you have some favorite documents that you would point me to as
most accurate or up to date?
No, because I haven't used ZODB documentation much myself. :)
Decent clues will be enough to get started.
- Doc in test or so
On Sep 13, 2006, at 3:42 AM, Edward K. Ream wrote:
Thanks to all who replied. The pointer to the correct
documentation will be
most helpful.
I just awoke (at 2 a.m.) with the way forward. In true prototype
fashion,
Leo's new zodb-read and zodb-write commands will simply disallow
multip
On Sep 12, 2006, at 8:24 AM, Edward K. Ream wrote:
This is a repost of my original: Can Leo use zodb as a file system.
Both the title of the thread and the botched formatting may have
put people
off, so let's try again :-)
I know Leo. :-) It's cool.
Benji's email is the right reply. I'l
On Jul 26, 2006, at 12:52 PM, Chris McDonough wrote:
FWIW I believe by default at least, open ZODB connections are tied
to the thread which did the opening (they are returned to a pool
when closed and reused, possibly in another thread). And indeed
each connection does have a cache; cachi
On Jun 26, 2006, at 3:16 PM, Florent Guillaume wrote:
On 26 Jun 2006, at 21:11, Robert Gravina wrote:
On 2006/06/27, at 3:49, Benji York wrote:
Robert Gravina wrote:
I just tried loading a persisted object interactively and
noticed that although the _p_oid doesn't print out as anything
On Jun 26, 2006, at 3:11 PM, Robert Gravina wrote:
I seemed to have solved this problem. I was able to write a __eq__
function like this:
def __eq__(self, other):
if isinstance(other, ):
if hasattr(other,"_p_oid") and other._p_oid != None and
(other._p_oid == self._
On Apr 29, 2006, at 6:08 AM, Christian Theune wrote:
Hi everybody,
the ZODB team is proud to announce a technical preview of a Blob
implementation for ZODB.
Hey.
This seems like there's no way that it will make it into the next
ZODB release, right?
I assume no one is using it in product
I proposed putting a persistent queue in ZODB (actually persistent)
and had gotten some positive feedback here. Jim and I talked over
some of the pros and cons today and I decided to just put it in a
separate package, in a separate product. It's here:
http://svn.zope.org/zc.queue/
The cu
On Mar 24, 2006, at 9:11 AM, Chris Withers wrote:
Hi All,
What happens if you call _p_deactivate() on a modified object but
before the modifications have been committed?
Do the modifications get lost or will they still be saved when the
next commit happens after the _p_deactivate()?
Un
On Mar 23, 2006, at 3:21 PM, Chris Withers wrote:
Hi All,
I was wondering whether anyone had implemented a FIFO persistent
queue class which has the following conflict resolution strategy:
two concurrent adds: adds both new items to the end of the queue in
a time-based order
one add an
On Mar 2, 2006, at 10:03 PM, Chris McDonough wrote:
persistence-3.6.0.egg (which would include persistent and BTrees
modules).
zodblib-3.6.0.egg (which would include ZODB and ZODB packages).
transaction-3.6.0.egg (which would include only the transaction
package).
zconfig-2.3.1.egg (which
On Feb 3, 2006, at 9:12 AM, Florent Guillaume wrote:
Gary Poster wrote:
On Jan 26, 2006, at 10:16 PM, Gary Poster wrote:
I have some code that might be worth putting into ZODB.
There are three bits.
- Two flavors of persistent queue.
[...]
I'm a bit surprised there was so l
On Jan 26, 2006, at 10:16 PM, Gary Poster wrote:
I have some code that might be worth putting into ZODB.
There are three bits.
- Two flavors of persistent queue.
[...]
I'm a bit surprised there was so little discussion: ZC has needed a
persistent queue several times in the past. Wh
I have some code that might be worth putting into ZODB.
There are three bits.
- Two flavors of persistent queue. Both have a conflict resolution
policy to be about as lenient as I could make it. They don't expect
to ever hold multiple instances of equivalent values at the same
time. One
On Dec 1, 2005, at 12:04 PM, Tim Peters wrote:
Note that we have yet to use a new strategy for shrinking pickle
sizes: a
few years ago Python's pickle code grew support for "extension
codes", a
registry of class/type names that _can_ be referenced by short (as
short as
2 bytes) new pickle
On Dec 1, 2005, at 11:38 AM, Tim Peters wrote:
... I know Gary Poster gave a lot of thought to making pickles for
the timezone info in Zope3 efficient too.
For some definition of "a lot of thought". :-) The pickle for
pytz.utc is now relatively small (though still adds a n
On Aug 5, 2005, at 2:33 PM, Tim Peters wrote:
[Julien Anguenot]
...
The order argument could be an integer with a default value to 0
added
to the registration method.
[Gary Poster]
I usually like the word 'priority' for this sort of value, rather
than
'order'. T
On Aug 5, 2005, at 6:20 AM, Julien Anguenot wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I would like to order the before commit hooks on a transaction by
being
able to specify an order for a subscriber at registration time. For
the
moment, they are called in the order they'v
On Jul 12, 2005, at 1:46 PM, Jens Vagelpohl wrote:
On 12 Jul 2005, at 18:17, Lennart Regebro wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
If it create
On May 5, 2005, at 11:24 PM, Gary Poster wrote:
I can't get Zope 3 to run
Sorry, that should have been "I can't get Zope 3 to serve pages"...
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
Z
On May 5, 2005, at 8:40 PM, Tim Peters wrote:
...I'd
be happier not finishing this exercise <0.5 wink>, so TM.begin() it
is.
I'm guessing this thread has to do with the recent _synch changes in
transaction._manager.py. I can't get Zope 3 to run without the
following change to the HEAD (which
45 matches
Mail list logo
