I think mysqldump does not provide this option. You can extract the data into a file and use "load data infile 'file_name replace into table_name" or replace into table_name select * from old_table_name; For the above to work, there need to be primary key or unique index. If primary key or unique index is not present, it would just insert the data.
Extrating data into a file will take lot of time if the data set is too huge. regards anandkl On Thu, Mar 11, 2010 at 3:32 AM, Don Read <don_r...@att.net> wrote: > On Mon, 8 Mar 2010 14:14:09 -0800 John Oliver said: > > > OK, a Drupal site I deal with has two copies... a production site and a > > test site. After new changes are developed, they're put on the test > > site. Once the test site is deemed to be OK, that entire site and > > database will be copied over to the production site. > > > > The issue is, while that work is taking place, changes are still > > happening on the production site, like new user registrations and some > > form input. What I'm thinking is, we can dump the affected tables and > > then import them into the test site, which started life as a mirror copy > > of the production site. If I were to: > > > > mysqldump -h db_server -h user -pPASSWORD database table_1 table_2 > > > /tmp/db.sql > > Get the table layout on the production box: > mysqldump --add-drop-table ... > > > > On the production side, and then: > > > > mysql -h test_db_server -h user -pPASSWORD database < /tmp/db.sql > ... > > -- > Don Read don_r...@att.net > It's always darkest before the dawn. So if you are going to > steal the neighbor's newspaper, that's the time to do it. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=anan...@gmail.com > >
