469,647 Members | 1,769 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,647 developers. It's quick & easy.

mysql backup

Doubt.
Backup of the database.

Example:

CREATE DATABASE prova;
CREATE TABLE `test` (`progressivo` tinyint(3) unsigned NOT NULL
auto_increment,`testo` char(50), PRIMARY KEY (`progressivo`))
TYPE=MyISAM;

insert into test (testo) values ('prova1');
insert into test (testo) values ('prova2');
If I make a delete from < nometabella > and does not come to me reset
the auto_increment (from version 4 is necessary to use truncate) is,
second me, a large anomaly the fact that if I make a backup of the
database with mysqldump and then subsequently (for disastry recovery)
a restoration the database, I do not obtain the same one database of
which I have made the backup. In fact the value of auto_increment
leaves again from 1.

example:

delete from test;

insert into test (testo) values ('prova4');

select * from test;

+-------------+--------+
| progressivo | testo |
+-------------+--------+
| 3 | prova3 |
+-------------+--------+
delete from test;

If

insert into test (testo) values ('prova5')

the value of progressivo is 4

If backup database with mysqldump and delete database prova and
restore it

insert into test (testo) values ('prova5')

the value of progressivo is 1
MysqlDump not create a backup, create a similar database, not equal
database!!!!!



xabaras
Jul 19 '05 #1
0 1530

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by James | last post: by
4 posts views Thread by Neil | last post: by
1 post views Thread by Konrad | last post: by
reply views Thread by Duane Winner | last post: by
4 posts views Thread by news | last post: by
reply views Thread by newman | last post: by
6 posts views Thread by frank78 | last post: by
4 posts views Thread by Bootstrap Bill | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.