stored? Why isn't this done automatically as it is for [ISAM] tables?
As for the why, I'm not a MySQL developer, but I believe the reason
goes something like this: When ISAM tables were implemented, they did
it the wrong way. When other table types came along, they fixed
this bug and do it the
stored? Why isn't this done automatically as it is for [ISAM] tables?
As for the why, I'm not a MySQL developer, but I believe the reason
goes something like this: When ISAM tables were implemented, they did
it the wrong way. When other table types came along, they fixed
this bug and do it
sql, query (*sigh*, I hate this filter)
I have an auto_increment key set up on my InnoDB table.
Whenever I delete all the records, the number isn't reset.
However, for my ISAM tables, whenever I delete all the
records, the auto_increment number is reset.
Is there a reason for this in InnoDB? Is
DobrĂ½ den,
sexta-feira, 25 de outubro de 2002, 14:26:05, napsal jste:
CB sql, query (*sigh*, I hate this filter)
CB I have an auto_increment key set up on my InnoDB table.
CB Whenever I delete all the records, the number isn't reset.
CB However, for my ISAM tables, whenever I delete all the
CB
CB However, for my ISAM tables, whenever I delete all the
CB records, the auto_increment number is reset.
CB Is there a reason for this in InnoDB? Is there a way that I
CB can reset the auto_increment number when all the records
CB are deleted?
try exec this query:
alter table TABLE_NAME
At 11:26 -0500 10/25/02, Chris Boget wrote:
sql, query (*sigh*, I hate this filter)
I have an auto_increment key set up on my InnoDB table.
Whenever I delete all the records, the number isn't reset.
However, for my ISAM tables, whenever I delete all the
records, the auto_increment number is