And now for a question about a completely different app (no sharding,
very simple). I haven't got a sufficient response from the pylons
group, so I'm trying here.
The question:
http://groups.google.com/group/pylons-discuss/browse_thread/thread/cb48d0ea2b084159
Things I've tried/considered:
diana wrote:
And now for a question about a completely different app (no sharding,
very simple). I haven't got a sufficient response from the pylons
group, so I'm trying here.
The question:
http://groups.google.com/group/pylons-discuss/browse_thread/thread/cb48d0ea2b084159
Things I've
Le lundi 11 janvier 2010 à 15:55 -0800, diana a écrit :
And now for a question about a completely different app (no sharding,
very simple). I haven't got a sufficient response from the pylons
group, so I'm trying here.
The question:
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
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
I never really suspected that this was a SQLAlchemy issue, which was
why I didn't originally post this question to the SQLAlchemy group. I
apologize if it came across that way.
Time for me to do my python VM homework...
My apologies,
--diana
On Mon, Jan 11, 2010 at 8:15 PM, Michael Bayer
