[Grok-dev] Re: browsing and modifying persistent objects in zodb

[Uli Fouquet]

Hi there,

Craeg Strong wrote:

> I would like to see full capability for editing/replacing/creating new 
> objects, where some of that functionality may be provided via escaping to
> an interactive session, for example a little TTW interface to a python 
> interpreter.  
> The ability to dynamically/interactively fix "broken" objects in my app 
> in ZODB would be IMO a major use case for this facility.

I have not much experience with broken objects, although I managed the
admin UI to recognize and delete broken objects on request (something,
that is difficult with the stock Zope 3 UI).

To build such a feature (fixing of broken objects) I would appreciate
any hints on how people cope with that problem normally. Please note,
that you can often start your Grok instance in debug mode (`bin/zopectl
debug`). Then you get a Python interpreter with the ZODB data available,
where you can modify objects manually. How would you fix any broken
objects in such an interactive Python shell at least in simple use cases
(vanished attributes for instance)?

Any hints?

Kind regards,

-- 
Uli

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20080622/9aa8b465/attachment.bin