You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/faq.rst
+28Lines changed: 28 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1465,6 +1465,9 @@ re–written, if possible it is suggested that you upgrade to take
1465
1465
advantage of the new features. For additional help on this subject,
1466
1466
look for the word "upload" in this document.
1467
1467
1468
+
Note: For errors while importing of dumps exported from older MySQL versions to newer MySQL versions,
1469
+
please check :ref:`faq6_41`.
1470
+
1468
1471
.. _faq6_6:
1469
1472
1470
1473
6.6 How can I use the relation table in Query-by-example?
@@ -2130,6 +2133,31 @@ Parameters should be prefixed with a colon(:) and when the "Bind parameters" che
2130
2133
these parameters will be identified and input fields for these parameters will be presented.
2131
2134
Values entered in these field will be substituted in the query before being executed.
2132
2135
2136
+
.. _faq6_41:
2137
+
2138
+
6.41 I get import errors while importing the dumps exported from older MySQL versions (pre-5.7.6) into newer MySQL versions (5.7.7+), but they work fine when imported back on same older versions ?
If you get errors like *#1031 - Table storage engine for 'table_name' doesn't have this option*
2142
+
while importing the dumps exported from pre-5.7.7 MySQL servers into new MySQL server versions 5.7.7+,
2143
+
it might be because ROW_FORMAT=FIXED is not supported with InnoDB tables. Moreover, the value of
2144
+
`innodb_strict_mode <http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_strict_mode>`_ would define if this would be reported as a warning or as an error.
2145
+
2146
+
Since MySQL version 5.7.9, the default value for `innodb_strict_mode` is `ON` and thus would generate
2147
+
an error when such a CREATE TABLE or ALTER TABLE statement is encountered.
2148
+
2149
+
There are two ways of preventing such errors while importing:
2150
+
2151
+
* Change the value of `innodb_strict_mode` to `OFF` before starting the import and turn it `ON` after
2152
+
the import is successfully completed.
2153
+
* This can be achieved in two ways:
2154
+
2155
+
* Go to 'Variables' page and edit the value of `innodb_strict_mode`
2156
+
* Run the query : `SET GLOBAL `innodb_strict_mode` = '[value]'`
2157
+
2158
+
After the import is done, it is suggested that the value of `innodb_strict_mode` should be reset to the
0 commit comments