SQLite rollback() fails - sqlalchemy

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion SQLite rollback() fails
Received-SPF: neutral (google.com: 216.168.135.167 is neither permitted nor denied by best guess record for domain of mike...@zzzcomputing.com) client-ip=216.168.135.167;
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=default; d=zzzcomputing.com;
  b=FsiaJhez8M/V7GwSQQkobYWU+L4x1SvsFkaJVDC1tSmMXFESccrIzdGgQ+WpyPEpGzKBQ93LFqBj84C4uBs43hF9qe7hDdX7j6cWJDJTOe1cx27JkHA/pcHxb3Zd/4aB  ;
From: Michael Bayer <mike...@zzzcomputing.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-35--544295212
Subject: Re: [sqlalchemy] SQLite rollback() fails
Date: Wed, 3 Oct 2012 11:19:35 -0400
In-Reply-To: <860B8F36-66F6-4095-9460-4B938FE05BA6@zzzcomputing.com>
To: sqlalchemy@googlegroups.com
References: <F685237642C8674A99FCFE0F4A4A217B07D5E...@OYWEX0202N3.msad.ms.com> <860B8F36-66F6-4095-9460-4B938FE05...@zzzcomputing.com>
Message-Id: <812F40A8-8B2B-487E-8034-2C6B724A0...@zzzcomputing.com>


--Apple-Mail-35--544295212
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 3, 2012, at 10:34 AM, Michael Bayer wrote:

>=20
>=20
> Catching both of these is easy enough and a patch is added to #2583: =
http://www.sqlalchemy.org/trac/ticket/2583
>=20
> The SQLite case you describe isn't exactly like either of these; if =
the object were flushed by the session and received the same PK, that =
case is already handled since the object would be in ._new.  So my only =
guess is that, that's not the trigger of the issue.    So at the very =
least you need to try that patch and see if it clears things up.
>=20
> Assuming that's the fix, I don't know that there's a clean way to =
patch this in, except for patching your install or monkeypatching a new =
Session class in.     I should have it committed in both 0.7/0.8 within =
30, unless I hit some snags in the tests.


OK those are in tip for default + 0.7, so you can get those fixes now =
from the snapshot releases.   =20=

--Apple-Mail-35--544295212
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 3, 2012, at 10:34 AM, Michael Bayer =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><br><div><div><br></div></div><div><div>Catching both of these is easy =
enough and a patch is added to #2583:&nbsp;<a =
href=3D"http://www.sqlalchemy.org/trac/ticket/2583">http://www.sqlalchemy.=
org/trac/ticket/2583</a></div><div><br></div><div>The SQLite case you =
describe isn't exactly like either of these; if the object were flushed =
by the session and received the same PK, that case is already handled =
since the object would be in ._new. &nbsp;So my only guess is that, =
that's not the trigger of the issue. &nbsp; &nbsp;So at the very least =
you need to try that patch and see if it clears things =
up.</div><div><br></div><div>Assuming that's the fix, I don't know that =
there's a clean way to patch this in, except for patching your install =
or monkeypatching a new Session class in. &nbsp; &nbsp; I should have it =
committed in both 0.7/0.8 within 30, unless I hit some snags in the =
tests.</div></div></div></blockquote><div><br></div><div><br></div><div>OK=
 those are in tip for default + 0.7, so you can get those fixes now from =
the snapshot releases. &nbsp; &nbsp;</div></div></body></html>=

--Apple-Mail-35--544295212--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
