On 06/11/2010 07:21 AM, Brian Moon wrote: > On 6/10/10 5:29 PM, Brian Aker wrote: >> Hi! >> >> I was just looking at this code yesterday, and I believe I have one >> of the fixes in my tree to be pushed. >> >> One thing about fixing datetime that I am worried about is the >> 000-00-00(...) issue. I am wondering how many people rely on being >> able to use that instead of NULL. > > Only in our entire code base. =) > > You see, NULL from a mysql table is (maybe was) kind of evil in PHP as > it sets the variable = null. Actually, it does not set the variable at > all in some cases. So, you end up with an unset variable. So, long ago, > many people quit using NULL in mysql tables for PHP applications. Sucks > eh? We adapted in some cases where needed to support both 0 and NULL. > But, for dates, we rely heavily on 0000-00-00 to mean not set.
Seems like having the php driver perhaps have a behavior more like what you want it to have would be better? As-in- perhaps we can get the php-drizzle driver to not set the variable to null when it gets a null on a datetime column? _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
