I subscribe to this list and saw your question.
What exactly are you trying to move to/from?
From: William Pettersson [mailto:wpettersson@stripped]
Sent: Wednesday, July 09, 2008 6:40 AM
Subject: Duplicating tables - mysqldump or mysqlpp or?
The short and dirty question:
I need to replicate 3-4 tables over a network from a remote MySQL
database to a local MySQL database, from within a (Visual) C++ app. My
choices as I see them are
a) Use mysql++, query the remote database first, retrieve all data, then
reinsert into the local database using mysql++
b) Just call mysqldump as a shell program.
Which would you guys suggest? Of note is the fact that how long it
takes me to write is important, so if the mysql++ way is going to take
longer (which it may, don't know how easily I can convert SELECT output
into an INSERT statement) then I'd prefer to stick with mysqldump.
For this project, I have a main DB server, and a remote handheld (eeepc)
client. The eeepc needs to query a serial device (RFID reader), check
some stuff in the database and show some info. The thing is, the eeepc
won't always have a network connection. Actually, it rarely will. So
what I need to do is synchronise two databases, remote and local, and
then just have my app query the local database.
I've got the app itself working, and querying the local database, so I
just need to work on the synchronising bit. I can either use mysqldump
(easy, dirty shell command), or pull info in with mysql++, rewrite the
output as an insert statement, and then reinsert with mysql++. I don't
want to waste too much time, so if mysql++ method is going to be too
hard, I'll just fall back to mysqldump.
07 5495 2944
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus