> "Dan Muey" <[EMAIL PROTECTED]> wrote: > > > > I have a table that I create with=20 > > > > CREATE TABLE SuperTest ( > > ID int(11) NOT NULL AUTO_INCREMENT, > > Name varchar(64) NOT NULL, > > Domain varchar(64) NOT NULL, > > PRIMARY KEY(ID) > > ); > > > > I use that same thing to create a the same table on two servers. > > > > On one server (mysql Ver 11.16 Distrib 3.23.49, for > > portbld-freebsd4.6 = > > (i386)) > > If I add, say five records I get ID to be 1,2,3,4,5. > > Then I delete ID 5 and insert a new record and it's id is > 6. So now I = > > have 1,2,3,4,6. > > That's what I want it to do. > > However on the other server (mysql version ???) if I have > 1,2,3,4,5, = > > delete ID 5=20 > > and insert a new one it makes the new one ID 5. I suppose > because it's = > > the next number. > > > > I'm not really even sure what to call it besides 'non reusable = > > auto_increment'. > > > > I can't seem to find anything on mysql.com about what settings, > > version, = etc cause it to work either way. > > It depends on table types. AUTO_INCREMENT values are reused > for BDB and ISAM tables and not reused for MyISAM and InnoDB tables.
Ooooohhhhh cool! So if I want to reuse them and know 100% they will be reused I need to specify the type as BDB or ISAM. And if I want to not reuse them and know 100% for sure they won't be reused I need to dpescify MyISAM or InnoDB. That's were my problem lay I believe, I never specified the table type and just let it happen as it felt like. Lesson learned! Thanks a million! DMuey > > > > Any insight would be greatly appreciated as in some situations I > > really = need it to be one way or the other consistently across > > servers. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
