Andrei Bautu added a comment - 20/Jul/08 07:17 AM - edited
I still believe that sequence reset belongs to ddl. Yes, it uses some data (max(id)) which will be retrieved by dml, but the workhorse should be in ddl (with a generic bootstrap method in dml).
Instead of copy/pasting the same code for each driver type, this approach would allow statements to be reuse per db type. For example, like in the case of CREATE SEQUENCE, CREATE TABLE, etc, ALTER TABLE xyz AUTO_INCREMENT value it's the same for MySQL no matter what driver type you use (adodb, pdo, native).
Andrei Bautu added a comment - 20/Jul/08 07:17 AM - edited I still believe that sequence reset belongs to ddl. Yes, it uses some data (max(id)) which will be retrieved by dml, but the workhorse should be in ddl (with a generic bootstrap method in dml).
Instead of copy/pasting the same code for each driver type, this approach would allow statements to be reuse per db type. For example, like in the case of CREATE SEQUENCE, CREATE TABLE, etc, ALTER TABLE xyz AUTO_INCREMENT value it's the same for MySQL no matter what driver type you use (adodb, pdo, native).
Instead of copy/pasting the same code for each driver type, this approach would allow statements to be reuse per db type. For example, like in the case of CREATE SEQUENCE, CREATE TABLE, etc, ALTER TABLE xyz AUTO_INCREMENT value it's the same for MySQL no matter what driver type you use (adodb, pdo, native).