[ postfixadmin-Bugs-1699218 ] not MySQL strict compliant
Brought to you by:
christian_boltz,
gingerdog
From: SourceForge.net <no...@so...> - 2007-10-09 17:03:37
|
Bugs item #1699218, was opened at 2007-04-12 13:24 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1699218&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: not MySQL strict compliant Initial Comment: Trying to run the database script on a database with strict mode is an exercise in futility. Why dates are stored as 0000-00-00 instead of being proper nulls? ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2007-10-09 17:03 Message: Logged In: YES user_id=1761957 Originator: NO Hmm... I had no idea MySQL had a 'strict' mode. Anyone know how to do this? Would making it compliant with 'strict' mode affect PostgreSQL compatibility? (I suspect not, but it's something to be careful about) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1699218&group_id=191583 |