Re: [sqlalchemy] difference between query.count() and query.all(), concurrency?

2011-02-20 Thread fred . haze
hi Michael, strangely enough when querying like you hinted i only get one row "uniqueified" again. So i must be missing still more of how this should work. My database nicely shows two rows queried with sql (Products and Products_descripition joined, filtered by a products_id), with python

Re: [sqlalchemy] difference between query.count() and query.all(), concurrency?

2011-02-20 Thread fred . haze
Hello Michael, thank you (all) for sqlalchemy :) The "uniquifying" had me spooked, and i am afraid it got me confused completely about connections, sessions, autoflushing and all the wonderful toys. Still don't know what a good pattern would be. I now even flush() and commit() directly after

[sqlalchemy] difference between query.count() and query.all(), concurrency?

2011-02-20 Thread fred . haze
Hi listmembers, i have a problem with a difference i find playing with sqla between query.count and query.all results. I have a parent class declaratively mapped to a table in MySQL, there is a child class with a relationship. I'm not sure how to create a quick session (i suspect a problem lies