On Fri, Apr 2, 2010 at 21:08, Bo Shi bs1...@gmail.com wrote:
Hrm, some different errors pop up. I'll move the dialog to the ticket
in question.
http://www.sqlalchemy.org/trac/ticket/1757
Should be fixed now (hopefully). Could you test once more?
Thanks,
--
Gaëtan de Menten
--
You
Hey everyone,
Is it the expected behavior that after querying an object with
`session.query(...).autoflush(False)...` and modifying some of its
fields still makes it issue UPDATE when a relation of the object is
referenced?
Let me illustrate what I mean precisely. First I query the Page class:
On Apr 9, 2010, at 4:51 PM, nekto0n wrote:
Hi there!
I'm now in the process of migrating from pure kinterbasdb to
SQLAlchemy. Everything is fine except for speed of insertions and
maybe updates. After some time of profiling I found out that a
significant amount of time is spent on getting
On Apr 11, 2010, at 4:28 PM, Peteris Krumins wrote:
Hey everyone,
Is it the expected behavior that after querying an object with
`session.query(...).autoflush(False)...` and modifying some of its
fields still makes it issue UPDATE when a relation of the object is
referenced?
Let me
Yesterday I downloaded 0.6beta3 and it took 27 seconds against 41 on
0.5. Pretty good results.
2010/4/10 Michael Bayer mike...@zzzcomputing.com:
nekto0n wrote:
Hi there!
I'm now in the process of migrating from pure kinterbasdb to
SQLAlchemy. Everything is fine except for speed of insertions
Wow. That was fast =)
Thanks for the fix. I'm a bit confused with results on 0.6beta3. Timer
showed significant speed boost and profiler (and breakpoint in
_CursorFairy) didn't show attempts to get rowcount. Am I doing
something wrong?
On Apr 12, 2:39 am, Michael Bayer mike...@zzzcomputing.com
