[sqlalchemy] use of a column label in HAVING clause

I dont understand what I'm doing wrong in the following situation. If I put this: case(whens={exclude_table.c.minutes_limit != None: exclude_table.c.minutes_limit}, else_=5000).label (name='minutes_limit') in the select clause of my query, I can't say: having=(func.sum(cdr_table.c.duration)

[sqlalchemy] Re: use of a column label in HAVING clause

On Thu, Apr 23, 2009 at 6:01 AM, Grimsqueaker grimsqueake...@gmail.comwrote: I dont understand what I'm doing wrong in the following situation. If I put this: case(whens={exclude_table.c.minutes_limit != None: exclude_table.c.minutes_limit}, else_=5000).label (name='minutes_limit') in

[sqlalchemy] after a week or so of working fine, my app starts experiencing sqlalchemy recursion issues

It starts with the code below, and the last two lines in visit_select and in process repeat indefinitely until the recursion error is generated i can't wrap around why this would happen -- i thought I had bad sql or something similar, but restarting the app completely fixes this issue. like

[sqlalchemy] Re: after a week or so of working fine, my app starts experiencing sqlalchemy recursion issues

clearly you have to figure out what runs on your server or what cache clears itself on tuesdays, and also we'd need to see the actual error message in your stacktrace. the trace is probably a distant side effect of something else happening (passing a None or something). Jonathan Vanasco

[sqlalchemy] Re: after a week or so of working fine, my app starts experiencing sqlalchemy recursion issues

and what is the query that goes plop? and whereabouts in the code? u can use sys.setrecursionlimit( x) to eventualy move the threshold down and make it die in other occasions too. On Thursday 23 April 2009 18:55:11 Jonathan Vanasco wrote: It starts with the code below, and the last two lines

[sqlalchemy] Re: puzzling outerjoin in the mapper

Hi, Mike, should I file a ticket for this?... or I just misinterpreted the result? sandro *:-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to

[sqlalchemy] Re: after a week or so of working fine, my app starts experiencing sqlalchemy recursion issues

On Thu, 23 Apr 2009 12:45:44 -0400 (EDT) Michael Bayer mike...@zzzcomputing.com wrote: clearly you have to figure out what runs on your server or what cache clears itself on tuesdays, and also we'd need to see the actual error message in your stacktrace. the trace is probably a distant

[sqlalchemy] Re: after a week or so of working fine, my app starts experiencing sqlalchemy recursion issues

Michael- There are no jobs on the server. This is happening on a small Pylons site that gets ~10k hits a week; I ran a bench of 30k hits on my dev machine, and couldn't recreate. But on the server it happens every week. If i restart on Monday, it happens on Monday; Tuesday - Tuesday, etc. The

[sqlalchemy] Re: Session-related best practice advice

This solves my case. Bummer I've found that out just now. Anyway, thought this post might help a bloke or two... No need to worry, should help some blokes mainly because that design decision usually is not self-evident (single session for multiple threads contra a session-per-thread will

[sqlalchemy] django middleware or signals for sqlalchemy Session

I would like to know if there is a consensus on the best way to set up and remove sqlalchemy Sessions in django. I figure I'm either going to use middleware, something like this thread: http://groups.google.com/group/django-users/browse_thread/thread/e6749f7eec1cc46c/ef9d9e27943af830 or I'm

[sqlalchemy] Re: django middleware or signals for sqlalchemy Session

Hi, On Thu, Apr 23, 2009 at 4:05 PM, davidlmontgomery davidlmontgom...@gmail.com wrote: I would like to know if there is a consensus on the best way to set up and remove sqlalchemy Sessions in django. I figure I'm either going to use middleware, something like this thread:

[sqlalchemy] intermittent problem using MSBit with sqlite

Hi, This is a kind of a shot in the dark, but I figure maybe someone else has run into the same thing. We use MySQL exclusively, except during unit tests, where we use sqlite. Our schema has some columns with type 'BIT' (and cannot be easily change), so they're defined as the SA type MSBit.