From: Rafal Somla
Date: July 28 2009 5:19am
Subject: Re: Please advise [Re: Restore locking: TRUNCATE resets AUTO_INCREMENT
 on InnoDB]
List-Archive: http://lists.mysql.com/backup/10
Message-Id: <4A6E8A44.2030205@sun.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=UTF-8
Content-Transfer-Encoding: 8BIT

Hi,

Ingo Strüwing wrote:
> Still we would have two options to make this safe:
> 
> A) Explicitly transport the auto_increment value.
>    A.1) Since the value is part of the meta data of a table in the
>         backup image, we could modify si_objects to save the value
>         in a context object so that the value used to create the last
>         table can be queried from si_objects. However, this means that
> 	si_objects will have to parse the serialization string.

I want to note that A.1) might be possible without parsing the serialisation 
string (I mean, parsing the CREATE TABLE statement). Since serialization string 
produced by si_objects can consist of several sub-strings, it is possible that 
the value of auto_increment is appended to it in a form which is easy to 
retrieve at restore time.

>    A.2) Accept the problem until we change the backup image format.
>    A.3) Do A.1 now and change it after A.2 is implemented.
>         But the A.1 code cannot go away for backward compatibility.
>

Rafal