<div class="gmail_extra">Maybe portability. If you try to port all the tables to Oracle, for instance, auto-increment would never work. But if you control the sequences in a separate table, it becomes highly portable.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Don't know if the people who first developed Vtiger were thinking this way...but it's definitely a good way to think!<br><br><div class="gmail_quote">2012/4/26 Adam Heinz <span dir="ltr"><<a href="mailto:amh@metricwise.net" target="_blank">amh@metricwise.net</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What is the use of tables like vtiger_picklist_seq when the<br>
vtiger_picklist.picklistid primary key is already defined as<br>
auto_increment? If you need the picklistid, just call ADOdb<br>
Insert_ID() after the fact. I know they're trivial little things, but<br>
there's more than one hundred _seq tables cluttering up SHOW TABLES.<br>
_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>
</blockquote></div><br></div>