Ah. Missed that. Thanks!
On Jan 15, 12:20 pm, Michael Bayer <[email protected]> wrote: > On Jan 13, 2012, at 11:47 AM, cbc wrote: > > > > > > > > > > > Hi: > > > I'm using SQLAlchemy 0.7.4 and I've been getting deprecation warnings, > > e.g., > > > a_column = Column(Integer(unsigned=True), nullable=True) > > > results in > > >SADeprecationWarning: Passing arguments to type object constructor > > <class 'sqlalchemy.types.Integer'> is deprecated > > > ...which is OK for now, but for the life of me, I cannot figure out > > how to resolve this in the future. Is unsigned int going away in > > future revisions? Is there a different way to specify unsigned ints? I > > cannot find anything in the docs but maybe I'm not reading them > > correctly. > > > Any pointers? > > > Please advise. Thanks. > > unsigned int is a MySQL type extension. If you need to specify that for your > MySQL database, use MySQL's type: > > from sqlalchemy.dialects.mysql import INTEGER > > INTEGER(unsigned=True) > > http://www.sqlalchemy.org/docs/dialects/mysql.html#sqlalchemy.dialect... -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. 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.
