Welcome to the LimeSurvey Community Forum

Ask the community, share ideas, and connect with other LimeSurvey users!

upgrade from 2.05+ SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect date

  • fdussurget
  • fdussurget's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
6 years 5 months ago #159283 by fdussurget
Hi there,
I'm stuck when upgrading from 2.05+ to 2.06+ or 2.71 ...

Full log is down here :

Erreur non récupérable durant la mise à jour. Détails de cette erreur :
CDbCommand n'a pas pu exécuter la commande SQL : SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '0000-00-00 00:00:00' for column '391372X194X2855' at row 644. The SQL statement executed was: ALTER TABLE `lime_survey_391372` CHANGE `token` `token` varchar(35) COLLATE 'utf8_bin'

Veuillez corriger cette erreur dans la base de données et recommencer.



LimeSurvey
Version 2.06+ Build 160129
Sommaire du rapport de profilage (Durée: 0.50617s, Memoire: 6,340KB)
Fonction Nb Total (s) Moy. (s) Min. (s) Max. (s)
system.db.CDbCommand.execute(ALTER TABLE `lime_survey_391372` CHANGE `token` `token` varchar(35) COLLATE 'utf8_bin') 1 0.02509 0.02509 0.02509 0.02509
system.db.CDbCommand.execute(ALTER TABLE `lime_tokens_685361` CHANGE `token` `token` varchar(35) COLLATE 'utf8_bin') 1 0.01314 0.01314 0.01314 0.01314
system.db.CDbCommand.execute(ALTER TABLE `lime_tokens_29419` CHANGE `token` `token` varchar(35) COLLATE 'utf8_bin') 1 0.01226 0.01226 0.01226 0.01226
system.db.CDbCommand.execute(ALTER TABLE `lime_survey_137142` CHANGE `token` `token` varchar(35) COLLATE 'utf8_bin') 1 0.00873 0.00873 0.00873 0.00873
system.db.CDbCommand.query(SHOW FULL COLUMNS FROM `lime_survey_611242`) 1 0.00721 0.00721 0.00721 0.00721

etc. etc.

Thank you for your help !
The topic has been locked.
  • LouisGac
  • LouisGac's Avatar
  • Visitor
  • Visitor
6 years 5 months ago #159284 by LouisGac
The topic has been locked.
  • fdussurget
  • fdussurget's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
6 years 5 months ago #159285 by fdussurget
Thank you ... So I should disable this NO_ZERO_DATE mode ?
The topic has been locked.
  • LouisGac
  • LouisGac's Avatar
  • Visitor
  • Visitor
6 years 5 months ago #159286 by LouisGac
The topic has been locked.
  • fdussurget
  • fdussurget's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
6 years 5 months ago #159309 by fdussurget
Thanks a lot, it solved my issue.
I added this to my.cnf :
sql-mode="ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

former value was :
ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
The following user(s) said Thank You: LouisGac
The topic has been locked.
More
6 years 2 weeks ago #165085 by Sabowano_16007
I have the same problem. I just upgraded my Mac server; then installed mysql on 10.13.3. It installs without my.cnf. The only instructions I can find to fix this are no good, because there is no sample my.cnf included in the current Mac DMG distro. Can anyone please tell me - where can I find a sample my.cnf that the Mac will read; and where where should it be placed? Thanks for your time - it's much appreciated.
The topic has been locked.

Lime-years ahead

Online-surveys for every purse and purpose