Mark Atwood wrote: > > On Jul 24, 2008, at 8:20 AM, Monty Taylor wrote: > >> Mark Atwood wrote: >>> I say rip it out >>> >>> It's confusing to users. they think it's either a constraint, or it >>> actually saves storage. >> >> ++ >> >> Also, I think we can either have a mysqldump_to_drizzledump tool... >> and/or we can have a dbdump tool that can speak Drizzle and MySQL (and >> postgres? - maybe I'm reaching) and dump to an appropriate target >> syntax... > > > How hard will it be to make something links to libdrizzleclient and > libmysqlclient > > If that linkage is a nightmare, then something that connects to the > command line interfaces of the two systems.
Once we're done, this should not be hard. If it is, I consider it a bug and we'll fix it. There should be no issues linking to libdrizzle and libmysqlclient. (I mean, eventually) > Probably should be written in Perl or Python to handle all the > translation issues.. Actually I agree with this anyway. Already spoke with Michael Bayer from SQLAlchemy about getting a drizzle dialect done for that... it would be probably pretty easy to build a nice robust tool using SQLAlchemy in Python to do this for tons of dbs... without being bloatware. Monty _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
