[sqlalchemy] slow import

Hi, I've been looking into performance bottlenecks in my app and I noticed that importing the sqlalchemy module itself takes 100 msec. It might seem pedantic to be worried about 100 msec, but it seems like an unnecessary startup cost. Have you considered ways of making sqlalchemy modules faster

Re: [sqlalchemy] slow import

On Dec 6, 2009, at 11:09 AM, andres wrote: Hi, I've been looking into performance bottlenecks in my app and I noticed that importing the sqlalchemy module itself takes 100 msec. It might seem pedantic to be worried about 100 msec, but it seems like an unnecessary startup cost. Have you

[sqlalchemy] Long running transactions and sessions

Hi All, Let me preface this with: I know that long running transactions in a web app are a worse idea than that trying to forge steel in a mould made of butter. With that out of the way; I have inherited a django web app that connects to many databases (this isn't starting well). These databases

[sqlalchemy] string type passed to join's onclause

Hi, It seems that although would work fine in place of a ClauseElement when passed to filter(), but not so when passed to the onclause parameter of join() ? There doesn't seem to be anything in the ClauseElement class that will convert a string to something of type ClauseElement. Have I missed

[sqlalchemy] Re: string type passed to join's onclause

Sorry, I should have looked at the source first. sql.text(string) should fix it. On Dec 7, 5:22 pm, Kalium raymond.ma...@gmail.com wrote: Hi, It seems that although would work fine in place of a ClauseElement when passed to filter(), but not so when passed to the onclause parameter of