On Tue, Dec 27, 2011 at 10:36 AM, Seth Johnson <[email protected]> wrote:
> On Tue, Dec 27, 2011 at 10:15 AM, Terry Brown <[email protected]> wrote:
>> On Tue, 27 Dec 2011 00:53:06 -0500
>> Seth Johnson <[email protected]> wrote:
>>
>>> I read a bit of SQLAlchemy tonight, and it does seem promising.  Makes
>>> working with data as objects easy, and seems to promise to do the
>>> versioning.
>>
>> Ville's schema is worth looking at.  Also the Django ORM is neat,
>> although SQLAlchemy might make a regular python classes based framework
>> easier, not sure.
>
>
> I will, somewhat soon . . .
>
>
>> I think there are many places where Leo does something similar to
>>
>> for n in c.unique_nodes():
>>    blah blah
>>
>> which might be an issue for DB based outlines if the goal was to have
>> massive outlines - Leo doesn't do much lazy evaluation.
>>
>> Even for outlines only as large as the Leo code base for example I
>> and even with a DB on the local machine I'd expect some performance
>> hit, although RAM disk buffering can help a lot of course.
>
>
> My approach would scale globally very easily, but yes, traversal might
> get intensive in some contexts.  I think optimizing that could be done
> locally and/or in the interface rather than the backend -- no reason
> why you couldn't just do the massive query, then build a list of child
> nodes pointer structure locally on that "cursor set."


And note: using an index on the parent key seems to be a very
effective way to do the traversal -- but I haven't tried it on massive
outlines.


Seth

> In the ancient world, the good designs supported bottomless sized
> structures, by just moving a window through it, swapping pieces into
> memory and on the display.  Plus, shockingly enough: my system
> actually allows the return of record-oriented db approaches -- it
> solves the problem of how to work with arbitrarily complex relational
> structure across networks (the basic technical issue that really
> killed dBASE and settled us on SQL) -- you can navigate through
> "tables" and "relations" record-by-record with all the facility with
> which one used to do it using dBASE on the old 8 bit office desktop.
> The horror!: database development for the masses again, with a
> BASIC-like language, now all over the net!  :-)

-- 
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.

Reply via email to