On Jul 22, 9:02 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On Jul 22, 2009, at 8:48 PM, Randy Syring wrote:
well this is really easy to analyze, turn on echo=debug and see what
SQLite is returning. The mapping of SQLite names to SQLA column types
in the 0.5 series is in
-Original Message-
From: sqlalchemy@googlegroups.com
[mailto:sqlalch...@googlegroups.com] On Behalf Of Randy Syring
Sent: 23 July 2009 07:23
To: sqlalchemy
Subject: [sqlalchemy] Re: autoload of db view treating
columns as Decimal
Well, I am not really sure what the problem
I work with the OP. The columns are correctly typed and the
reflection code seems to work correctly with views that are directly
selecting from tables. Its when a view selects from another view that
we have problems with the type being lost.
Can anyone else say for sure whether it is supported
On Jul 22, 2009, at 8:48 PM, Randy Syring wrote:
I work with the OP. The columns are correctly typed and the
reflection code seems to work correctly with views that are directly
selecting from tables. Its when a view selects from another view that
we have problems with the type being
it is news to me that SQLAlchemy's table reflection code would even read a
SQLite view (and that sqlite had views, actually).Make sure your
view defines character based fields as VARCHAR, CHAR or similar.
note that SQLite has a very casual notion of types so you can make up any
type names