Hi guys,
I will be blogging about this with more detail in the next few days but
want to give you the heads up here in about the changes to drizzledump.
So basically over the last couple of weeks I've done almost a complete
re-write of Drizzledump. The new code *should* do exactly the same as
before (minus a couple of things like xml output) and has an important
new feature: MySQL migration.
What it now does is basically auto-detect if it is connecting to a MySQL
or Drizzle server. If it is connecting to a MySQL server it will
convert the table schemas and some data (for example 0000-00-00 dates
become NULL, TIME data becomes an INT) on-the-fly. Creating a Drizzle
compatible output.
As an extension to this there is the new --destination-type=database
option along with the other --destination-* options. This means that
you can use drizzledump to dump from a MySQL server directly to a
Drizzle server without needing an intermediate .sql file.
I urge anyone playing with drizzle to please try these features out, I
have no doubt there will be a few bugs in my code and edge cases I have
missed (nobody is perfect ;). The more feedback we can get the better,
so I would love to hear about anything you think may be missing or could
be done slightly differently.
The code is in trunk right now and will be in the release due this week.
--
Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
