Thanks. That sounds pretty labor intensive, since I'd have to do the copy
for each table. That makes the process much harder to automate. And I'm not
sure the end result would be what I wanted anyway. I would like to be able
to do this without copying data around. Does anybody have another
Is there a set of flags for mysqldump that will include the auto_increment
specifier for columns, but leave out the AUTO_INCREMENT=x saved values?
I want to compare the schema of two versions of a database, without
considering the data. In my opinion, the saved auto increment counter is
part of
You can import your data into a test database,then export the data using
statement select ... into ...
then You can complare the two.
On Tue, May 20, 2008 at 9:14 AM, Dan Lipsitt [EMAIL PROTECTED] wrote:
Is there a set of flags for mysqldump that will include the auto_increment
specifier for
Figured out what was causing it
The /etc/my.cnf had a line in it, in the [mysqldump] section...
compatible=mysql40
Comment that line out and it works - we need that when sending data to
customers who are still running mysql40.
Now I know whats causing it, I can work around it.
Many thanks,
Hi,
I got confused looking to see if this was a known problem - so thought I'd
try again.
mysql_standard 4.1.16 on Linux...
Synopsis:
Create table with auto_increment
mysqldump database
output doesn't create table with auto_increment.
Example:
Create a table in a junk database using,
create
Imran,
Thanks for your reply.
I tried what you asked, and it did the same.
I then went onto a couple of other boxes with EXACTLY the same MySQL install
and they worked (added the auto_increment).
The box that fails is running Redhat 7.3 (for customer backward
compatibilty). I dont have any other
The reason I asked about auto_increment behavior is that I'm looking at
the output from mysqldump --opt and there are no commands to preserve/set
the auto_increment value. Is there a mysqldump option to do this? Or
will restoring from a dump always leave the auto_increment value one
greater
Hello
I am using MySQL v4.0.18. I am using the mysqldump program to do backups. I was
wondering how, if at all, does mysqldump preserver the auto_increment value?
When using phpmyadmin, there is an option to preserve the auto_increment value and the
resulting file has something like
-Original Message-
From: Tucker, Gabriel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 11:36 AM
To: Mysql General (E-mail)
Cc: Philip Antoniades (E-mail)
Subject: mysqldump and auto_increment
Hello
I am using MySQL v4.0.18. I am using the mysqldump program to do backups.
I
Hello.
I've just created a table with a auto_increment column. I then did
ALTER TABLE tbl AUTO_INCREMENT=4711;
Now, when I insert one row into this table, it get's 4711 as the
auto_increment column's value. However, dumping this table with
mysqldump --opt DB tbl
loses the auto_increment
) Ltd t/a RedTie
Durban, South Africa
Cell (+27-83) 262-9163
Office (+27-31) 767-0249
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
]On Behalf
Of Alexander Skwar
Sent: 17 July 2001 21:58
To: [EMAIL PROTECTED]
Subject: mysqldump loses auto_increment
Hello
So sprach »Warren van der Merwe« am 2001-07-17 um 22:31:02 +0200 :
in my plain language there it is, but the pro's may give a more detailed
approach.
Yeah, that's sorta how I understand it as well. Also auto_increments
BREAK when you manually insert a row and set the column with the
auto_inc.
At 11:03 PM +0200 7/17/01, Alexander Skwar wrote:
So sprach »Warren van der Merwe« am 2001-07-17 um 22:31:02 +0200 :
in my plain language there it is, but the pro's may give a more detailed
approach.
Yeah, that's sorta how I understand it as well. Also auto_increments
BREAK when you
values into an
AUTO_INCREMENT column, make sure the number you are inserting hasn't already
been used or you won't like the results.
Gerald Jensen
- Original Message -
From: Alexander Skwar [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 17, 2001 2:58 PM
Subject: mysqldump loses
14 matches
Mail list logo
