Shawn, I'd actually considered such, but I was hoping for it to already be present. I'm currently on a tight deadline to finish a project I'm working on so devoting time to getting 'mysqldump' stable enough to then propagate across corporate servers in such a short period is not very likely.
As far as your comment regarding replication vs syncing, I have noticed the same thing. And it really blows my mind that so few people are interested in two-way syncing (e.g. I'll give you mine and you give me yours). This seems to be a necessity, and the very foundation for many corporate applications, yet it also apears that most are aparently proprietary. Anyway, thanks again for your input. Regards, Michael ---------- Original Message ---------------------------------- From: [EMAIL PROTECTED] Date: Thu, 16 Feb 2006 15:31:04 -0500 >My suggestion: Modify the source of mysqldump yourself. > >After all, it is open source. Make sure you adhere to any and all >licensing requirements and copyright notices and you will keep yourself >out of any legal trouble. > >For the vast majority of users, replication is a better solution than what >you propose so the changes you propose haven't been discussed at all. If >others would like to have your changes, perhaps you would consider >synching your mods with the main development tree and releasing them to >the community? > >Shawn Green >Database Administrator >Unimin Corporation - Spruce Pine > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
