|
From: Ben C. <php...@be...> - 2002-11-04 03:23:43
|
The reason to use the sequence tables in mysql comes down to using the database abstraction library. Though many of the database software packages support something like auto_increment (mysql), native sequence (postgres) and identity (mssql), not _all_ databases have a similar functionality. As a result, the authors of PEAR::DB decided to use sequences -- native ones, such as with postgres, or emulated via *_seq tables. Of course, just because it works, that doesn't mean it's the best solution, but it is a rather portable one. The time may come when I rework the database stuff so that all database access is tweaked to the strengths of the various database packages, but that time isn't right now. :) On Sat, Nov 02, 2002 at 12:25:15AM +0100, Patrick Mairif wrote: > Hi Ben, > > when copying all bugtracker data into a new database (because of release > switches) it was more than once confusing to me, why the bugtracker > itself tries to create new datasets with an id of 1. Now I found out, > that you use aditional *_seq tables to remember the id for the next dataset. > > Why? MySQL has a nice auto_increment feature, PostgreSQL has sequences > and I'm sure oracle has sth. similar! > > ...and hey, great work. I was surprised what happend in the last months! > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > phpbt-dev mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpbt-dev |