Re: dump, drop database then merge/aggregate

2016-02-29 Thread Steven Siebert
Ah, ok, if I understand correctly within this context every record in the one table _should_ have a unique identifier. Please verify this is the case, though, if for example the primary key is an auto increment what I'm going to suggest is not good and Really Bad Things will, not may, happen. If

Re: dump, drop database then merge/aggregate

2016-02-29 Thread Steven Siebert
Totally with you, I had to get up and wash my hands after writing such filth =) On Mon, Feb 29, 2016 at 12:14 PM, Gary Smith wrote: > On 29/02/2016 16:32, Steven Siebert wrote: > >> >> At risk of giving you too much rope to hang yourself: if you use >> mysqldump to dump the database, if you use

Re: dump, drop database then merge/aggregate

2016-02-29 Thread Gary Smith
On 29/02/2016 16:32, Steven Siebert wrote: At risk of giving you too much rope to hang yourself: if you use mysqldump to dump the database, if you use the --replace flag you'll convert all INSERT statements to REPLACE, which when you merge will update or insert the record, effectively "mergin

Re: dump, drop database then merge/aggregate

2016-02-29 Thread lejeczek
On 29/02/16 16:32, Steven Siebert wrote: What level of control do you have on the remote end that is collecting/dumping the data? Can you specify the command/arguments on how to dump? Is it possible to turn on binary logging and manually ship the logs rather than shipping the dump, effectively

Re: dump, drop database then merge/aggregate

2016-02-29 Thread Steven Siebert
What level of control do you have on the remote end that is collecting/dumping the data? Can you specify the command/arguments on how to dump? Is it possible to turn on binary logging and manually ship the logs rather than shipping the dump, effectively manually doing replication? I agree with o

Re: dump, drop database then merge/aggregate

2016-02-29 Thread Johan De Meersman
- Original Message - > From: "lejeczek" > Subject: Re: dump, drop database then merge/aggregate > > today both databases are mirrored/identical > tonight awkward end will dump then remove all the data, then > collect some and again, dump then remove > and

Re: dump, drop database then merge/aggregate

2016-02-29 Thread lejeczek
On 29/02/16 15:42, Gary Smith wrote: On 29/02/2016 15:30, lejeczek wrote: On 28/02/16 20:50, lejeczek wrote: fellow users, hopefully you experts too, could help... ...me to understand how, and what should be the best practice to dump database, then drop it and merge the dumps.. What I'd like

Re: dump, drop database then merge/aggregate

2016-02-29 Thread Gary Smith
On 29/02/2016 15:30, lejeczek wrote: On 28/02/16 20:50, lejeczek wrote: fellow users, hopefully you experts too, could help... ...me to understand how, and what should be the best practice to dump database, then drop it and merge the dumps.. What I'd like to do is something probably many have

Re: dump, drop database then merge/aggregate

2016-02-29 Thread lejeczek
On 28/02/16 20:50, lejeczek wrote: fellow users, hopefully you experts too, could help... ...me to understand how, and what should be the best practice to dump database, then drop it and merge the dumps.. What I'd like to do is something probably many have done and I wonder how it's done best.

dump, drop database then merge/aggregate

2016-02-28 Thread lejeczek
fellow users, hopefully you experts too, could help... ...me to understand how, and what should be the best practice to dump database, then drop it and merge the dumps.. What I'd like to do is something probably many have done and I wonder how it's done best. A box will be dumping a database (m