Hi Jobin,
On 06/09/10 19:46, Jobin Augustine wrote:
The Idea is good.. a good to have feature.. but..
During the porting work of drizzledump to windows, noticed that
drizzledump got lots of dependency on files in:
drizzled\internal\* and others.
to be exact.. total 26 other source files it touches!.
I hope many of these complexity should go off.
Yes, I already plan to kill much of this off in a separate effort as
much of it is mysys legacy. I'm slowly going through and cleaning up
the clients code when I can.
To connect to mysql server and pull the data, IMHO we should not be
stregthening this dependency again.
The only extra dependency would be on libdrizzle, which is a dependency
for drizzledump anyway. Libdrizzle does a very good job of talking to
MySQL servers.
On the otherway,
if user gets mysql dumps files generated by mysqldump. drizzledump can
be made to read data from it.
I hope this will be easier and cleaner to implement.
This was the original plan, but after some discussions we believe having
the tool do the dirty work for you would be preferred.
But saying this I added at the end of that a future expansion to cover
that. It could easily become a phase 3.
there is another advantage too.. it will be easier to make it read
postgres or oracle dumps too.
allowing migrations from other planets too.. :)
That is another good future feature for it :)
Kind Regards
--
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
