On MSSQL the default nullableness of a column, when neither NULL or NOT NULL are specified in the column definition, is configurable. The MSSQL dialect produces ANSI standard SQL when creating tables. So when a Column is specified with nullable=True, the DDL emitted contains neither NULL or NOT NULL. If the database is not set to use the ANSI null default, this produces unexpected results.
I'm not sure what the policy is about things like this. Would you welcome a patch that always explicitly applied either NULL or NOT NULL to column definition DDL produces by the MSSQL dialect? It might lead to some people being surprised by the behavior of their tables, but it seems (to me) to be the best way to assure that there are no future surprises. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
