> > Sorry...change "which" constraint naming pattern? > > I'm not tracking what the problem is so following your directions to fix it has me a bit lost.
What I think you are saying is that SQL alchemy is creating a check(0,1) constraint for my boolean fields on the mysql server And that something about one of the template strings in the naming convention does not like it?? But I'm not clear how I can provide a better "constraint naming pattern" if the disable trick does not work... I'll go read the docs you linked now and see if that explains it for me, but wanted to respond quickly given the day ;-) Happy New Year & thanks again! Dewey -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
