Closed caliginous closed 7 years ago
Get the same error when using it on drupal
"DB Error: unknown error"
Part of the debug log:
Hi @caliginous and @mjvanhaastert - I ran into this problem too. I'm guessing you're running MySQL 5.7, which has stricter controls on "sql_mode". For instance, if you run this in MySQL:
show variables LIKE 'sql_mode';
You'll probably see something like:
+---------------+----------------------------------------------------------------------------------------------------------------
| Variable_name | Value |
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------+
| sql_mode | 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 |
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)
"NO_ZERO_DATE" is just what it sounds like - in newer versions of MySQL, the default is to disallow putting in zeroes for a date, which this extension does.
I just submitted a patch - but if you don't know how to merge it, it just involves removing the "created date" line from xml/auto_install.xml
.
That's awesome, it worked. Thank you so much for replying!
On 7 April 2017 at 23:21, Jon notifications@github.com wrote:
Hi @caliginous https://github.com/caliginous and @mjvanhaastert https://github.com/mjvanhaastert - I ran into this problem too. I'm guessing you're running MySQL 5.7, which has stricter controls on "sql_mode". For instance, if you run this in MySQL:
show variables LIKE 'sql_mode';
You'll probably see something like:
+---------------+---------------------------------------------------------------------------------------------------------------- | Variable_name | Value | +---------------+-------------------------------------------------------------------------------------------------------------------------------------------+ | sql_mode | 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 | +---------------+-------------------------------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.01 sec)
"NO_ZERO_DATE" is just what it sounds like - in newer versions of MySQL, the default is to disallow putting in zeroes for a date, which this extension does.
I just submitted a patch - but if you don't know how to merge it, it just involves removing the "created date" line from xml/auto_install.xml.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/veda-consulting/uk.co.vedaconsulting.mailchimp/issues/269#issuecomment-292665798, or mute the thread https://github.com/notifications/unsubscribe-auth/ABKMiDIF4Fw4fmZCRREXfJek5afCdil7ks5rtrbrgaJpZM4MzYt- .
Thanks that did solve the problem for me to
Hey there, this is a workaround which I think will stop working at some point as MySQL has decided 00000 dates are bad (see https://stackoverflow.com/questions/22806870/incorrect-datetime-value-database-error-number-1292)
The above PR fixes the issue
Hello
Am using 2.0 and latest civicrm on wordpress. When I hit install I get this error:
"DB Error: unknown error"
Any ideas?
Dan