]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1fbed90) | patch
Don't commit failed transaction
authorMike Bayer <mike_mp@zzzcomputing.com>
Thu, 19 Oct 2017 01:17:00 +0000 (21:17 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Thu, 19 Oct 2017 01:17:00 +0000 (21:17 -0400)
commit1210f49bb5a691324a55b4c3bf4600c359f396a9
treeb8615a32522d9c65717c3b835572eeccbb1b3fb8tree | snapshot
parent1fbed902ede72e5a663b7e685843f0a8ed250c45commit | diff
Don't commit failed transaction

The test here commits even though integrityerror
was raised due to the fixture.  Postgresql seems to allow
this even though it's usually strict about this.  remove
the requirement that a database needs to be able to
commit after an integrity error was raised.

Change-Id: I437faadb04ff7a9c3f624c68646b4f4f504b504a
lib/sqlalchemy/testing/suite/test_dialect.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git