On Tue, Sep 18, 2012 at 1:33 PM, Ids idsvandermo...@gmail.com wrote:
and of course sqlalchemy 0.5.1 did work. So something in sqlalchemy 0.7.8
broke...
I just hit this error myself when using the latest SQLAlchemy (both
0.7.9 and latest 'default' from hg) against MySQL 3.23.58. Adding the
On Mon, Oct 22, 2012 at 3:29 PM, Simon King si...@simonking.org.uk wrote:
On Tue, Sep 18, 2012 at 1:33 PM, Ids idsvandermo...@gmail.com wrote:
and of course sqlalchemy 0.5.1 did work. So something in sqlalchemy 0.7.8
broke...
I just hit this error myself when using the latest SQLAlchemy
Mmm. The traceback I got last (TypeError), only occurs on a client platform
(redhat 8.0) using mysql 3.23 client software. When run on a platform with
MySQL 5.0 (suse 10.1) software you're solution by raising the
NotImplemented exception works.
redhat 8.0 + mysql 3.23 client + python-mysql
We are using MySQL 3.23.31 on that machine :-)
It seems tx_isolation was added ad 4.0.3 (according to
http://dev.mysql.com/doc/refman/4.1/en/server-system-variables.html#sysvar_tx_isolation).
But if I add
if self.server_version_info (4, 0, 3):
raise NotImplementedError()
I get another
OK, that is good information there, I'll see if i can get the notimplemented to
not break like that.
On Sep 17, 2012, at 11:17 AM, Ids wrote:
We are using MySQL 3.23.31 on that machine :-)
It seems tx_isolation was added ad 4.0.3 (according to
OK, this is actually a different issue. I wonder if i can get a 3.23 version
running on a VM somewhere.
On Sep 17, 2012, at 11:17 AM, Ids wrote:
We are using MySQL 3.23.31 on that machine :-)
It seems tx_isolation was added ad 4.0.3 (according to
