the SERIAL type never gets used, though, if the value for the primary key is actually present when a row is INSERTed.
we might want to look into not having SERIAL specified (or AUTOINCREMENT in mysql) for any primary key column that also has a ForeignKey on it. all in agreement ? 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 > [email protected] > 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 [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
