> Do you know if this is a MySQL specific thing or does anytime Torque > encounter an integer primary key with idmethod=native, it assumes it's > an autoincrement? I don't have a clue how the templates handle this.
IIRC, at some point I remember not being able to set "defaultIdMethod" at the <database> level with PostgreSQL because of a similar problem--it would cause breakage if any particular table didn't have any primary keys because there was no key to autoincrement. I had to deal with this by setting "idMethod=native" explicitly on each <table> that had an autoincrement key. It's hard to call this a "bug", because it is really a disagreement about what the semantics of defaultIdMethod should be. IMO defaultIdMethod should only affect columns with autoIncrement="true", because in any non-trivial data model primary keys will not all be autoincremented. -- Bill -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
