List:Commits« Previous MessageNext Message »
From:Ingo Strüwing Date:October 23 2009 2:15pm
Subject:Re: bzr commit into mysql-6.0-backup branch (ingo.struewing:2879)
Bug#47484
View as plain text  
Hi Rafal.

Rafal Somla, 23.10.2009 15:31:

> Hi Ingo,
> 
> SATATUS: Approved.
> 
> SUGGESTION
> ----------
> I think that the new requirement that a backup engine must correctly
> save/restore auto_increment value for each table should be documented
> somewhere, but I don't know where :( I suggest adding a note to the bug
> for the docs team, so that when time comes we will make some decision on
> how to document this.
> 
> COMMENT: This is a near perfect patch! :)

Thank you. I'll add a note to the bug report.

Regards
Ingo
-- 
Ingo Strüwing, Database Group
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Geschäftsführer: Thomas Schröder,   Wolfgang Engels,   Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Häring   HRB München 161028
Thread
bzr commit into mysql-6.0-backup branch (ingo.struewing:2879) Bug#47484Ingo Struewing23 Oct
  • Re: bzr commit into mysql-6.0-backup branch (ingo.struewing:2879)Bug#47484Rafal Somla23 Oct
    • Re: bzr commit into mysql-6.0-backup branch (ingo.struewing:2879)Bug#47484Ingo Strüwing23 Oct
    • Re: bzr commit into mysql-6.0-backup branch (ingo.struewing:2879)Bug#47484Paul DuBois23 Oct
  • Re: bzr commit into mysql-6.0-backup branch (ingo.struewing:2879)Bug#47484Charles Bell23 Oct
    • Re: bzr commit into mysql-6.0-backup branch (ingo.struewing:2879)Bug#47484Ingo Strüwing23 Oct