sqlalchemy should accept u'3' AND 3 from sqlite db default values

[Former user]

First, thanks very much to Taavi for helping figure this out.

We were having trouble using meta.reflect() on CentOS with an sqlite db when the same code was running fine on Mac.

What we were trying to run:

self.engine = create_engine(url)
self.scheduler_db_meta = MetaData()
self.scheduler_db_meta.reflect(bind=self.engine)
self.scheduler_db_meta.bind = self.engine

Error: http://pastebin.com/9fF1vQHN

Looks like this is due to libsqlite returning default values differently - on the mac the default value comes back as u'3' instead of 3 (on centos)

STR:

>>> import sqlalchemy
>>> e = sqlalchemy.create_engine('sqlite:///foo.db')
>>> c = e.connect()
>>> r = c.execute('pragma table_info("foo")')
>>> r.fetchall()
[u'an', u'int', 0, u'3', 0)]((0,)
(on the mac)
versus:
[u'an', u'int', 0, 3, 0)]((0,)
(on centos)

This is also a bug on sqlite for not choosing one way to return the values across all OSes but it seems to me like even if they did, sqlalchemy should be prepared to accept either format.

[Mike Bayer]

missing here is the original table definition you're trying to reflect, else I can't reproduce this.

Also there was a behavioral change regarding sqlite default reflection that is specifically in 0.7.2 of SQLAlchemy - is this error with SQLAlchemy prior/later to 0.7.2, or both ?

[Mike Bayer]

K, I guess at some point we'll have to try out sqlite on two platforms with a table like this:

CREATE TABLE test (
  somecol INTEGER DEFAULT '3'
)

[Mike Bayer]

c7ab095fdbb13d045376df3f997a30058d7c82dd

33d741b2f3f95eef039ceb0e45a3a219399f2caf

[Mike Bayer]

Removing milestone: 0.7.9 (automated comment)