Boolean PassiveDefault('f') columns don't get default values under SQLite

[Former user]

Setting a PassiveDefault('f') on a Boolean column works under PostgreSQL. But under SQLite, new objects have that column incorrectly set to True. See the attached test case.

I'm using: SQLAlchemy 0.5.2 SQLite 3.6.9

[Former user]

test to demonstrate the bug

[Mike Bayer]

The PassiveDefault correctly assigns a default value of f to the column, where in SQLite there is no real "boolean" datatype - an INSERT into this table populates the column with the string value f.

The Boolean datatype in SQLAlchemy when applied to SQLite uses 1 and 0 for true/false values. So you should specify the value 1 with PassiveDefault in conjunction with SQLite.

PassiveDefault is not intended to be backend agnostic.

[Mike Bayer]

Removing milestone: 0.5.xx (automated comment)