Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#5 not MySQL strict compliant

open
nobody
Database (41)
5
2013-12-01
2007-04-12
Anonymous
No

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?

Discussion

  • GingerDog
    GingerDog
    2007-10-09

    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)

     
    • milestone: --> SVN_(please_specify_revision!)
     
  • Logged In: YES
    user_id=593261
    Originator: NO

    Gingerdog, you can real all the details on http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html

    The reporter unfortunately didn't mention where he found problems. According to grep, I think the problem is located in DATABASE_MYSQL.TXT which has several datetime fields with default '0000-00-00'.

    (Database design (especially encoding) and upgrading has to be discussed anyway. I'll start a thread on the -devel mailinglist.)