[sqlalchemy] SystemError: null argument to internal routine

2011-03-11 Thread robert rottermann
Hi there, when testing one of my routines I get a strange error. SystemError: null argument to internal routine this is the method I call: def getExistingDoktypes(self, typid=0): return tuple with ((typid, typ), ((typid1, typ1), (typid2, typ2), ..)) session =

Re: [sqlalchemy] SystemError: null argument to internal routine

2011-03-11 Thread robert rottermann
this was caused by some error erlier error that somehow messed up the test environment. thanks for listening robert Am 11.03.2011 10:23, schrieb robert rottermann: Hi there, when testing one of my routines I get a strange error. SystemError: null argument to internal routine this is the

[sqlalchemy] Django-like test fixtures via SQLAlchemy?

2011-03-11 Thread Todd Rowell
Hi All- I'm a long-time Django user who has become accustomed to Django's easy generation and loading of test fixtures (i.e., a known database state for testing) and I'm looking for something similar for SQLAlchemy. I've seen and been working with Kumar's fixture project (http://

Re: [sqlalchemy] Django-like test fixtures via SQLAlchemy?

2011-03-11 Thread Michael Bayer
On Mar 11, 2011, at 2:25 PM, Todd Rowell wrote: Hi All- I'm a long-time Django user who has become accustomed to Django's easy generation and loading of test fixtures (i.e., a known database state for testing) and I'm looking for something similar for SQLAlchemy. I've seen and been

[sqlalchemy] Re: Django-like test fixtures via SQLAlchemy?

2011-03-11 Thread Todd Rowell
Thank you for the response! However, I think I may have caused some confusion. Let me try to clarify... I'm a long-time Django user who has become accustomed to Django's easy generation and loading of test fixtures (i.e., a known database state for testing) and I'm looking for something

[sqlalchemy] Commit many queries at once

2011-03-11 Thread eddy
Like in session we commit all changes in one commit is there any way we can execute different queries at one. for eg q1 = some.table update.query1 q2 = some.table.update.query2 instead of updating table one at a time like running q1.execute() q2.execute() can i add these to a session and commit