On Jan 8, 2:50 am, jason kirtland [EMAIL PROTECTED] wrote:
This was a bug in the reflection of empty string defaults. Give r4029
on the trunk a try.
You're my hero -- for today, anyway. Thanks for the fast fix!
--~--~-~--~~~---~--~~
You received this message
I'm using mysql-5.1.15, sqlalchemy-0.4.2, mysql-python-1.2.2.
In SA-0.3, the docs read:
When Tables are reflected from the database using autoload=True, any
DEFAULT values set on the columns will be reflected in the Table
object as PassiveDefault instances.
This is not indicated behavior for
On Jan 8, 12:25 am, Michael Bayer [EMAIL PROTECTED] wrote:
passivedefaults are reflected in 0.4 just as they are in 0.3, as much
as the underlying database allows them to be discovered.
Thanks for the quick reply. I reduced this to a small example and it
seems the failure I'm encountering