Thanks, Phillip, that was enlightening
Rik
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
At 10:45 AM 11/9/00 +0100, Rik Hoekstra wrote:
>[rh]I've been following this thread. This may be a bit of a newbie question,
>but it's been bugging me for a while. I see how I can store propertysheets
>in Racks using ZClasses and Skinscripts, but the propertysheet term suggests
>that there should
At 09:18 AM 11/9/00 +0200, Roch'e Compaan wrote:
>
>I set "loaded by accessing attribute" to the attribute "id".
You should only do that if you want an "infinite rack". That is, one which
contains all possible objects. Using "id" means that if the Rack tries to
see if an object exists, it will
[rh]I've been following this thread. This may be a bit of a newbie question,
but it's been bugging me for a while. I see how I can store propertysheets
in Racks using ZClasses and Skinscripts, but the propertysheet term suggests
that there should always be an object that the properties are attache
> It's determined by the radio button setting on the Storage tab. If you
> neglected to set it to "loaded by accessing attribute " and
> fill in the
> blank, then your objects have been stored in the ZODB, as well as in the
> RDBMS.
>
Thanks.
I set "loaded by accessing attribute" to the at
At 10:51 PM 11/8/00 +200, Roch'e Compaan wrote:
>
>> The comment is perhaps misleading. What it means is that the _setSlot
>> call isn't needed if your Rack implements a non-ZODB storage mechanism.
>> The reason *why* it isn't needed, is that the DataSkin will ask for a
>> slot on demand, so tha
> I'm not sure I understand your question. If you don't have something
> special you want to do by subclassing Rack, then the answer would be
> "no". :)
You do answer my question below. I was wondering if this line would not
cause an object to be stored in the ZODB by default.
>
> The comme
At 06:10 PM 11/8/00 +0200, Roch'e Compaan wrote:
>In Rack.py I noticed the following:
>
>a = self.loadAttrib
>if not a:
>slot = self._writeableSlot(key)
>slot[SelfKey] = item.aq_base# strip acquisition wrapping
>item._setSlot(slot)
