On Mon, Aug 9, 2010 at 10:11 AM, Terry Brown <[email protected]> wrote:
> I still think it would be a good idea to have a db abstraction layer in there > so you don't have to add zodb as a dependency. I agree. zodb must not be a dependency, especially for newbies. But that should not make any difference to the development: it should be possible to enable or disable zodb at will provided that zodb is available. > Write the abstraction layer (which should be intrinsically simple) and then > develop using zodb - you get the chance to switch to couchdb or sqlite (with > a probably trivial adapter) etc. etc. This is a separate issue. leoNodes.py contains some hooks for zodb. These are enabled when use_zodb is True. It is False in the official distribution. I had forgotten that the low-level vnode methods *always* set the v._p_changed attribute as required by zodb, regardless of the use_zodb switch. I have no objections to adapter code for DB's, but details like v._p_changed are much easier to build into the core. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
