[Grok-dev] schema.List returns a list, but is it persistent?

[Souheil CHELFOUH]

-1   Using the very basic python object doesn't prevent you from using your
own storage, behind the scene.
It has too much implications and cannot be changed. It makes no sense to
force a PersistentList

2009/8/27 Wichert Akkerman <wichert at wiggy.net>

> On 2009-8-27 11:13, Martin Aspeli wrote:
> > Sebastian Ware wrote:
> >> That is true, however I would definitely call that behaviour a bug in
> >> schema.List. The assumption that only data manipulation is done with
> >> applyData sounds risky. You could get some pretty creepy bugs...
> >>
> >> Anyway, I'll look into your suggestion.
> >>
> >> A suggestion is to change the behaviour of applyData so that it
> >> returns PersistentList.
> >
> > -1
> >
> > The implications for backwards compatibility are enormous.
>
> -1
>
> Using PersistentList also means you are now dependent on ZODB and can no
> longer user other storage options, for example SQLAlchemy via megrok.rdb.
>
> Wichert.
>
>
> --
> Wichert Akkerman <wichert at wiggy.net>   It is simple to make things.
> http://www.wiggy.net/                  It is hard to make things simple.
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/grok-dev/attachments/20090827/7bb246e2/attachment.html