On Mar 7, 2007, at 3:05 AM, Adam Groszer wrote:
Hello Dieter,
I meant the tracing storage only for testing/debugging purposes.
Might be a good idea to add a warning that it could/will be a big
performance penalty.
It isn't at all clear that it will be. Using event dispatchers is
slower t
Hello Dieter,
I meant the tracing storage only for testing/debugging purposes.
Might be a good idea to add a warning that it could/will be a big
performance penalty.
Tuesday, March 6, 2007, 8:26:48 PM, you wrote:
DM> Jim Fulton wrote at 2007-2-25 08:21 -0600:
>>It might also be nice to have this
Jim Fulton wrote at 2007-2-25 08:21 -0600:
>It might also be nice to have this generate events. That is, the
>tracing storage should call zope.event.notify.
>
>I intent in 3.8 or 3.9 to start having ZODB depend on zope.event. We
>really should have used events rather than adding the callback'
Hello Win,
I think you'll have to write a script.
Have a look at
http://svn.zope.org/z3c.zodbbrowser/sandbox/src/z3c/zodbbrowser/
From plugin_fs.py you can extract how to open the ZODB without zope.
You can then traverse (access the properties) of the root and object
thereunder.
Matching an OODB
Hello Christian,
It's mostly done. Available at z3c.zodbtracing as inbetween I figured
out that tracing the connection should be also possible.
Saturday, February 24, 2007, 8:00:40 PM, you wrote:
> Hi,
> I'm pretty sure there are no hooks around that do what you need.
> The methods you want to
On Feb 27, 2007, at 1:13 AM, Adam Groszer wrote:
Hello Jim,
What do you say,
One event type with parameters:
- method name
- method parameters
OR
Lots of event types with parameters:
- method parameters
Lots of event types that subclass a single event type.
That want if you want them all,
Hello Jim,
What do you say,
One event type with parameters:
- method name
- method parameters
OR
Lots of event types with parameters:
- method parameters
Sunday, February 25, 2007, 3:21:52 PM, you wrote:
> It might also be nice to have this generate events. That is, the
> tracing storage sho
On Feb 25, 2007, at 9:09 AM, Christian Theune wrote:
No, just create a new project. This doesn't have to be in the core
ZODB.
Storages can be defined in new python packages. Why don't you try
'z3c.tracingstorage'?
Excellent point,
Jim
--
Jim Fulton mailto:[EMAIL PR
Hi,
Am Sonntag, den 25.02.2007, 10:17 +0100 schrieb Groszer Adam:
> Hello Christian,
>
> Gosh, that looks simple. A simple decorator pattern on the storage.
Well. The storage API isn't as cleanly defined as it could be, but in
general the answer is yes. ;)
> So I shall create a branch, somethin
It might also be nice to have this generate events. That is, the
tracing storage should call zope.event.notify.
I intent in 3.8 or 3.9 to start having ZODB depend on zope.event. We
really should have used events rather than adding the callback's
we've added recently.
Jim
On Feb 25, 200
Hello Christian,
Gosh, that looks simple. A simple decorator pattern on the storage.
So I shall create a branch, something like
svn://svn.zope.org/repos/main/ZODB/branches/tracing-storage
from
svn://svn.zope.org/repos/main/ZODB/trunk
and start there?
Saturday, February 24, 2007, 8:00:40 PM, you
Hi,
I'm pretty sure there are no hooks around that do what you need.
The methods you want to tap into would be
store()
load*()
on the storages.
You might want to look into how the BlobStorage was created to make
yourself a "tracing storage" that can be wrapped around an existing
storage to all
Hello,
I'm using ZODB in a GUI application, so outside of Zope.
I'm having performance problems. I'm already on the way of figuring
out what causes a lot of object load. getTransferCounts helped in
that. But now I would need something more detailed.
Are there any hooks or something to get detail
13 matches
Mail list logo
