Hi,
This is a kind of a shot in the dark, but I figure maybe someone else
has run into the same thing. We use MySQL exclusively, except during
unit tests, where we use sqlite. Our schema has some columns with
type 'BIT' (and cannot be easily change), so they're defined as the SA
type MSBit.
Does anyone have any suggestions for managing both horizontal and
vertical partitioning within the same application? In particular I'd
prefer that most of my code be oblivious to all this and only use a
single session object. To make it a little more concrete, imagine I
have four tables in my
Hi,
I'm not sure if you're interested in this sort of report, but what the
heck. When I try to do a metadata.create_all(engine) on my relatively
simple 'declarative' class (see widget.py below), I get the backtrace
below if I'm using the latest (test) MySQL-python driver (1.2.3b1) (it
works fine
Hi,
I'm testing out the below script with MySQL 5.0.51a and SA 0.4.6.
Based on the documentation I expected to see a SAVEPOINT be created
(at some point) and rolled-back to but instead I get the following:
satest.doit()
2008-05-14 12:42:37,813 INFO sqlalchemy.engine.threadlocal.TLEngine.
is somewhat of a surprise to me)
2. the inner() method issues no SQL. add a sess.flush() in there,
and do away with threadlocal to see it work.
On May 14, 2008, at 3:45 PM, Jacob Gabrielson wrote:
from sqlalchemy import *
from sqlalchemy.orm import *
engine = create_engine('mysql://[EMAIL
