Re: [sqlalchemy] More efficient Insert mechanism

2010-02-02 Thread Mati Skiva
Michael Bayer wrote: matiskiva wrote: Naturally, the problem is that SA collects the generated id, that is why every statement is executed alone, and than the generated id is retrieved. I was wondering though, is there some kind of a more efficient mechanism? At least on MySQL, under

Re: [sqlalchemy] More efficient Insert mechanism

2010-02-02 Thread Mati Skiva
Michael Bayer wrote: Mati Skiva wrote: I believe I took these issues into account. But just to be sure, maybe you can highlight something for me. I assume the followings about the process of session.add: * after session.add is called, the objects are placed in a to-do pool (maybe

Re: [sqlalchemy] Re: releasing eager loaded resources

2010-02-01 Thread Mati Skiva
Michael Bayer wrote: matiskiva wrote: Just to skip the newbie replies :) I attempted to go over the rects collection and expunge all the items. This direct approach didn't work. expunging is not enough. did you expire the rects collection on each Detection object, and also remove any

[sqlalchemy] Re: Better eager loading

2009-11-02 Thread Mati Skiva
Michael Bayer wrote: On Nov 1, 2009, at 8:10 AM, matiskiva wrote: The sql query to perform the eager loading is horrible, more horrible than anything i can imagine. This is certainly an exaggeration, and its always a good idea to please tell us on the list what output you're