Re: [sqlalchemy] handling the results of `session.execute`

2016-02-05 Thread Mike Bayer
On 02/05/2016 05:32 PM, Jonathan Vanasco wrote: I've run into a few cases where I need to abandon the ORM and run `session.execute()` horrors Usually... I'm doing a bunch of nested queries and only pull out a `count` or a few rows of 1-2 id columns. Writing in pure sql is faster (for me),

[sqlalchemy] handling the results of `session.execute`

2016-02-05 Thread Jonathan Vanasco
I've run into a few cases where I need to abandon the ORM and run `session.execute()` Usually... I'm doing a bunch of nested queries and only pull out a `count` or a few rows of 1-2 id columns. Writing in pure sql is faster (for me), gives me more control, and avoids having to do a

Re: [sqlalchemy] handling the results of `session.execute`

2016-02-05 Thread Jonathan Vanasco
On Friday, February 5, 2016 at 6:03:11 PM UTC-5, Michael Bayer wrote: horrors > i know :/ why not call result.scalar() ? > ignorance. result.scalar() I think is what you're looking for yep! > -- You received this message because you are subscribed to the Google Groups