Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.4(EOL), 10.5
-
None
Description
splitted from Roel's comments in MDEV-33494:
https://jira.mariadb.org/browse/MDEV-33494?focusedCommentId=280959&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-280959
https://jira.mariadb.org/browse/MDEV-33494?focusedCommentId=280955&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-280955
I think we should just set the sql_mode to the default instead of trying to fixing it in the spider init queries to fix any other potential failures of the same cause.
Attachments
Issue Links
- split from
-
MDEV-33494 spider plugin init failure with no_zero_date sql_mode
-
- Closed
-
Hi holyfoot, ptal thanks
upstream/bb-10.5-ycp 1d7bfeed64fead00ae1b73e8d53a7dc2cf78e549
MDEV-33584 Use the default SQL_MODE for spider init queries
This should fix all future problems caused by a non-default global
sql_mode from the server where spider is to be installed.