SQLObject is my favourite ORM. Very pythonic at the front end, transparently SQL at the back.
On Tue, Mar 26, 2013 at 4:42 AM, Don Dwiggins <[email protected]>wrote: > On 3/24/13 8:26 AM, Terry Brown wrote: > >> >> 3) Leo using a DB as a storage mechanism. This really has to be for >> some reason, presumably to enable other items in this list. Not sure >> if there's a performance boost here without lazy loading, which is a >> big implementation issue, particularly for searches etc. Also, unless >> you read the whole outline from the DB at once, I'm not sure about >> performance on hierarchical data like Leo's. Postgresql supports >> `WITH RECURSIVE` which could fetch subtrees in one request, not sure >> about other DBs. Maybe not a problem with non-sql DBs. >> > If you're going to use a DB, take a look at SQLAlchemy, particularly the > ORM layer. You could achieve a level of independence from a particular > DBMS, and might find it useful to have an object model. > > -- > > Don Dwiggins > Advanced Publishing Technology > > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > leo-editor+unsubscribe@**googlegroups.com<leo-editor%[email protected]> > . > To post to this group, send email to [email protected]. > Visit this group at > http://groups.google.com/**group/leo-editor?hl=en<http://groups.google.com/group/leo-editor?hl=en> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
