Steve Alexander wrote:
>
> Michael Bernstein wrote:
>
> > I am currently planning two separate 'Archive' type
> > projects/Products. In both cases, I need to make sure that
> > my implementation will scale to hundreds of thousands or
> > even millions of objects.
> >
>
> > In one project the o
Steve Alexander wrote:
>
> This assumes a method of DataSkins.DataSkin _uncache_attrs:
>
> def _uncache_attrs(self, names):
> v=self._v_attrCache
> for name in names:
> del v[name]
>
> I haven't tested any of this yet.
And I realized just after I sent it that the method should b
While debugging some dependencies in some of my SkinScript, I had an idea.
SkinScript could be extended so that COMPUTE statements can have a
RECOMPUTE FOR clause. This clause would tell a dataskin to invalidate
its cache for the attributes in the COMPUTE statement if any of the
attributes in
When debugging skinscript, especially tricky dependencies between what
gets computed when during state changes, do the following:
1: Run zope in debug mode (-D)
2: Put an external method called print_ in the root of your ZODB, with
the code:
def print_(s):
print s
3: In your SkinScri
Michael Bernstein wrote:
> I am currently planning two separate 'Archive' type
> projects/Products. In both cases, I need to make sure that
> my implementation will scale to hundreds of thousands or
> even millions of objects.
>
> In one project the objects are very simple ZClasses with a
> few
