> I could go either way on this, I just want consistency man, consistency :-)
Hehe, you're speaking my language. I'm all for consistency, I just think they're separate attributes (primary keys and autoincrements) that don't necessarily imply each other. 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. I can't say for sure (perhaps Martin or another committer can offer their advice?), but I'd imagine if you could hunt this down and submit the patch for fixing the idbroker to only take effect when autoincrement is specifically set and not just on any arbitrary integer primary key column comes along, someone will roll back the last patch and get the new one put in place. Thanks, Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
