I think zodb is overkill. Sqlite can do everything we'll ever need (including storing pickled uA's, indexed by gnx and uA name) -- Sent from my Nokia N900
----- Original message ----- > On Mon, 9 Aug 2010 07:14:38 -0700 (PDT) > "Edward K. Ream" <[email protected]> wrote: > > > 2. Using zodb as Leo's cache. leoNodes already contains the low-level > > code to do this. I'm going to revisit the caching code soon--it might > > be the time to re-imagine caching as a front end to zodb. That might > > allow Leo outlines to contain (that is, connect with) millions of > > nodes... > > 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. 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. > > Cheers -Terry > > -- > 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. > -- 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.
