the change to not produce SERIAL when a ForeignKey is present is committed in changeset 1664. MySQL already had this logic in place with regards to AUTO_INCREMENT.
On Jun 23, 2006, at 5:09 PM, Randall Smith wrote: > In a secondary table used for many to many relationships, usually a > foreign key exists for both tables. Each of those fields is both a > primary key and a foreign key. When defining a table with sqlalchemy, > any field with primary_key=True and Integer type is created as a > Serial > type. This is not appropriate for secondary tables since they use > values from their foreign keys. > > Randall > > > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Sqlalchemy-users mailing list > Sqlalchemy-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
