The subject says it. The currently available rpm for python-
sqlalchemy for fedora 11 is 0.5.2-2. What's the plan for updates?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this
Hi,
I'm getting the following error in one of my unit tests, while I have
never opened a subtransaction. The only thing that happens in that
test is that a first db_session.flush() raises an IntegrityError (this
is deliberate, because I test the generation of an unique number).
Then a second
not sure. rpms / pkgs etc. are handled independently of the
SQLAlchemy project itself, so you should poke around to see who has
created RPMs in the past.
On Jul 12, 2009, at 12:44 PM, Les wrote:
The subject says it. The currently available rpm for python-
sqlalchemy for fedora 11 is
On Jul 12, 2009, at 3:19 PM, Antoine Pitrou wrote:
Hi,
I'm getting the following error in one of my unit tests, while I have
never opened a subtransaction. The only thing that happens in that
test is that a first db_session.flush() raises an IntegrityError (this
is deliberate, because I
On 12 juil, 23:37, Michael Bayer mike...@zzzcomputing.com wrote:
the session always does things in a transaction , as does any DBAPI
connection running in the default mode of operation as according to
spec. Whether or not the Session leaves the transaction open after
an individual
On Jul 12, 2009, at 5:57 PM, Antoine Pitrou wrote:
Ok, thanks. Then I want to ask: why the complication? It looks like a
weird and difficult to grasp behaviour. Why doesn't a failed flush()
leave the session in a consistent state (either rolled back or not,
but not something in-between)?
Hello,
Thanks for the lengthy (!) explanation.
On Jul 13, 1:05 am, Michael Bayer mike...@zzzcomputing.com wrote:
Postgres in
particular has operations which, once failed, the transaction is not
allowed to continue:
Ouch. I'll have to change my strategy, then (I run unit tests with
On Jul 13, 1:33 am, Michael Bayer mike...@zzzcomputing.com wrote:
pysqlite doesn't seem to support SAVEPOINT out of the box. Jason
Kirtland found out a little bit about it here:
http://itsystementwicklung.de/pipermail/list-pysqlite/2009-June/00041...
. But I'm not sure how that can
