Hadar Pedhazur wrote:
[clarifications and opinions]
Hey,
I just wanted to chip in that:
* I'm very happy a foundation has been announced. This is what I and
others advocated for, starting in earnest after the castle sprint last
year. This is a major step in the right direction. Thank you
Lennart Regebro wrote:
OK, so becuase of the tomembased release schedule, let's not dicuss
what goes in 2.9. let's discuss what features we found most
urgent/desirable, so we can start working on that, like now.
I think it's fine to discuss what we want to be in Zope 2.9. This way we
can plan
As I mentioned before, I'd like to see Christian's blob work make it
into 2.9. So that's one feature. ;-)
On Mon, 2005-06-20 at 09:55 +0200, Martijn Faassen wrote:
Lennart Regebro wrote:
OK, so becuase of the tomembased release schedule, let's not dicuss
what goes in 2.9. let's discuss what
Hi everybody,
Martin Faassen wrote:
* I'm very happy a foundation has been announced.
Me too, and I am grateful to Zope Corp. for that.
* We all agree that the Foundation should be about more than just
vendors [...] We have extremely significant contributors in the community
[...]
It
Hi All,
As my ZODB data files become larger and larger I am looking at ways to make
the structure of my objects more efficient. To simplify my question, suppose
I have two different classes and both contain a list of a objects from a
third class:
class x has the attribute x.elements = [objects
As far as I am aware, ZODB will store a list of pointers to the lists of
z objects. What you should be careful of for efficient use of ZODB is
that your list is stored in an efficient way, well if the list is
updated often or long anyway.
When you pack your ZODB does it take up a lot less
[Yair Benita]
... suppose I have two different classes and both contain a list of a objects
from a third class:
class x has the attribute x.elements = [objects of class z]
class y has the attribute y.elements = [objects of class z]
As far as I understand python the lists x.elements and
[Laurence Rowe]
...
Unless you use a special PersistentList ZODB will have no choice but
to store a new copy of the whole list when that list is modified.
Caution: that's true of a PersistentList too. The purpose of
PersistentList isn't realy to supply more-effecient storage (that's
the
As always. Clear, detailed and to the point. Thanks Tim.
Actually, the z class isn't a subclass of persistent because it just
holds data (has no methods) and never changes. Same goes to the lists
of x and y, they tend to hold a few elements and also never change.
The X and Y classes are
[Yair Benita]
...
Reading this answer I understand that anything I store should be
persistent, even if its a list I don't plan to edit.
I wouldn't say that. For example, for _most_ applications it would be
foolish to create a subclass of Persistent to store an integer, as
opposed to just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Peters wrote:
[Yair Benita]
...
Reading this answer I understand that anything I store should be
persistent, even if its a list I don't plan to edit.
I wouldn't say that. For example, for _most_ applications it would be
foolish to create
FYI, for the few of you who may not actually listen to the
bigger lists ;-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Page
Sent: Monday, June 20, 2005 5:54 PM
To: zope@zope.org; zope-announce@zope.org
Subject: [Zope-Annce] Zope Foundation ideas
12 matches
Mail list logo
