Why should disabling caching prevent c.db being persistent? To me, it looks like disabling caching should only prevent reading/writing to c.db when dealing with cached tree representations for @file nodes, not prevent using *.db altogether.
On Sat, Jul 30, 2011 at 5:51 PM, Edward K. Ream <[email protected]> wrote: > On Sat, Jul 30, 2011 at 9:11 AM, Ville M. Vainio <[email protected]> wrote: >> On Sat, Jul 30, 2011 at 4:43 PM, Edward K. Ream <[email protected]> >> wrote: >> >>> Thanks for this. It's looking good. There is still and issue with >>> guarding c.db and g.app.db, but I'll just go ahead and resolve this. >> >> I don't think there is need to guard g.app.db, it's always available. >> c.db can be missing if the .leo document has no filename yet, g.app.db >> has no such issues.b > > It's a little more complicated than that. When caching is disabled, > the "db" variables could be None. As of rev 4444 of the trunk (also > containing the merge of the free_layout branch), the default g.app.db > and c.db is just {}. Later, this may be changed to a pickleShare > instance. > > The cacher.clearCache method now takes care to work with either > PickleShare instances or Python dictionaries. This seems to solve all > the problems. > > 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. > > -- 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.
