we have a full set of tests that ensure SQLA itself has no unreleased memory issues or excessive cycles and they've been in our trunk for several years, and we also nailed a few remaining corner cases over the past year which correspond to highly unusual usage patterns, so I'm very confident that there's no issues within SQLA itself.
On Jan 11, 2010, at 7:17 PM, Diana Clarke wrote: > On Mon, Jan 11, 2010 at 7:07 PM, Antoine Pitrou <solip...@pitrou.net> wrote: >> Le lundi 11 janvier 2010 à 15:55 -0800, diana a écrit : >> >> Well if you only want to count entries, use Query.count(), not >> Query.all(). > > Yup, I don't actually do this in a real app. I was just doing this (in > a hello world app) as an exercise to illustrate a point, and to better > understand pylons (and, as I'm just learning, the Python VM). > > Thanks Antoine, > > --diana > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
