Tim Peters wrote at 2005-8-26 14:59 -0400:
> ...
>I would like to make it an error (raise a ValueError exception) to attempt
>to set obj._p_changed to a true value when obj is a ghost. Does anyone
>object?
I came along an argument against this change:
Assume, you have a persistent object "o" w
On Wed, Aug 31, 2005 at 06:02:21PM -0400, Jim Fulton wrote:
| You might be right, but the only credible use case I've seen
| is to go last. The example Julien has something going first
| and something going last. Looking at the code, I don't see
| why the thing he wanted to go first needed to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ok this time I'm giving up. Not because you convinced me but because I
don't want to spend more energy on this since you'll have the last word
anyway.
You want to remove it, fine do it. Let's have several specific hook
ordering implementations on ever
Dieter Maurer wrote:
Jim Fulton wrote at 2005-8-31 10:20 -0400:
...
Thus my proposal could be seen as well as a request to change (or to
make more flexible) the policy already in place. (Which was my use case)
Except that, as Tim and I have pointed out, the order gimmic didn't
deal at all w
Jim Fulton wrote at 2005-8-31 10:20 -0400:
> ...
>> Thus my proposal could be seen as well as a request to change (or to
>> make more flexible) the policy already in place. (Which was my use case)
>
>Except that, as Tim and I have pointed out, the order gimmic didn't
>deal at all well with the use
Florent Guillaume wrote:
Jim Fulton wrote:
I don't understand why keeping the order paremeter is such a big deal ?
Because it clutters the ZODB API with something that is, fundamentally
application policy.
Ok seen that way I agree. That's not the ZODB's job to decide what kind
of API is
Julien Anguenot wrote:
Jim Fulton wrote:
...
I don't understand why keeping the order paremeter is such a big deal ?
Because it clutters the ZODB API with something that is, fundamentally
application policy.
Here we disagree.
I could agree if only one hook could be registred instead of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> Jim Fulton wrote:
>
>>> I don't understand why keeping the order paremeter is such a big deal ?
>>
>>
>> Because it clutters the ZODB API with something that is, fundamentally
>> application policy.
>
>
> Ok seen that way
Tim Peters wrote:
[Dmitry Vasiliev]
Since then I've changed my mind and almost haven't used setdefault(). So
now I'm only +0 on the idea. :-) I think pop() is even more useful than
setdefault(), I've planned to use it for some persistent queue
implementation (based on BTrees). So if setdefault(
Jim Fulton wrote:
I don't understand why keeping the order paremeter is such a big deal ?
Because it clutters the ZODB API with something that is, fundamentally
application policy.
Ok seen that way I agree. That's not the ZODB's job to decide what kind of
API is provided to enforce policy.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> Julien Anguenot wrote:
>
> I'm gonna respond to a number of emails at once. :)
>
>> Tim Peters wrote:
>>
>>> [Tim]
>>>
>>>
...
Julien provided links to code that already uses the new feature:
""" As an Indexati
Hello.
To inform you, i created branch alienoid-btrees_pop with pop() method
implementation. Tim was kind :) and told me he will review it on Thursday.
But if someone wants to take a look or have any suggestions - you are very
welcome.
Regards,
Ruslan
__
12 matches
Mail list logo
