At first glance, this looks really good to me. The only thing that makes my spider-sense tingle is this: any date data containing 0000-00-00 -> 0001-01-01
I agree we need a conversion, but what if the table also contains date data with '0001-01-01' (Who can say what depraved use of special dates exist out there?) ; ) Of course, we can document this heavily so people will know what to expect and can adapt as they see fit. It seems nicer than trying to think too much for the user. I've also been thinking about how to help you test this. We should be able to set up something with the randgen that will generate some random test beds, convert them to Drizzle, then do some validation queries. -Patrick On Mon, Sep 6, 2010 at 12:39 PM, Andrew Hutchings <[email protected]>wrote: > Hi guys, > > I'd really appreciate your feedback on the plan I have entered into the > whiteboard of the following blueprint: > > https://blueprints.launchpad.net/drizzle/+spec/drizzledump-mysql > > 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 >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
