Hey Patrick,
On 06/09/10 18:22, Patrick Crews wrote:
At first glance, this looks really good to me.
Thanks :)
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 totally agree, but I cannot yet see any way around this, which is why
I said that it should warn to stderr. Something like:
"Warning: table `t1` has data with the date '0000-00-00' which is
invalid in drizzle. This has been converted to '0001-01-01'."
Also we will need good documentation on this.
Although I'm open to suggestions if anyone has a better solution to this
issue.
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.
I was wondering how to apply this in dtr without having either a MySQL
server to hand or something simulating one (which feels like it will be
a lot of work).
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
