* Starting at root, check all objects if they are referenced,
* and produce a list of those which are not, for cleanup purposes.
* Packing the database cleans up in this manner.
Oh well. Third try:
I know about the 'pack database' button. Garbage collection of this
kind is not my problem.
extremely expensive. you would have to...
- assemble a list of all objects IDs in the ZODB
and then...
- parse all contents of all objects and check against that ID list.
you would probably need a little counter for every single ID that gets
incremented upon finding its ID referenced, and
[EMAIL PROTECTED] wrote:
* I have lots of scripts, dtml methods etc. everywhere which are
* perfectly well-known to the ZODB, nothing wrong with that, but which
* are simply not used by me anymore. No usage from other scripts nor
* methods nor documents. And these buggers I'd like to
[EMAIL PROTECTED] wrote:
I have lots of scripts, dtml methods etc. everywhere which are
perfectly well-known to the ZODB, nothing wrong with that, but which
are simply not used by me anymore. No usage from other scripts nor
methods nor documents. And these buggers I'd like to find.
They're
* I have lots of scripts, dtml methods etc. everywhere which are
* perfectly well-known to the ZODB, nothing wrong with that, but which
* are simply not used by me anymore. No usage from other scripts nor
* methods nor documents. And these buggers I'd like to find.
* There is no easy way to
Original problem:
I have lots of scripts, dtml methods etc. everywhere which are
perfectly well-known to the ZODB, nothing wrong with that, but which
are simply not used by me anymore. No usage from other scripts nor
methods nor documents. And these buggers I'd like to find.
@Steve:
You
On Fri, 30 Aug 2002 [EMAIL PROTECTED] wrote:
Consider a tab for methods... which allows to parse them and produces
a sortable list of links to the other referenced methods...
Just to make it clear what I'm talking about when I say effectively
impossible, consider the following bit of DTML:
On Fri, 30 Aug 2002 [EMAIL PROTECTED] wrote:
Consider a tab for methods... which allows to parse them and produces
a sortable list of links to the other referenced methods...
Good luck grin. You might manage a Quick and Dirty implementation,
but to guarantee you've not missed anything you
R. David Murray wrote:
On Fri, 30 Aug 2002 [EMAIL PROTECTED] wrote:
Consider a tab for methods... which allows to parse them and produces
a sortable list of links to the other referenced methods...
Good luck grin. You might manage a Quick and Dirty implementation,
but to guarantee
On Fri, 30 Aug 2002, Oliver Bleutgen wrote:
If there is a central part in zope (ZPublisher?) which always runs when
methods/scripts/etc are called, one could patch it to also log the path
of the object which is called (the physical path!).
Then just use a web spider which crawls the whole
10 matches
Mail list logo
