mysql 5.7 may have made SHOW VARIABLES limited

Issue #4007 resolved
Mike Bayer repo owner created an issue

per https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56 they've changed the rules for SHOW.

At https://github.com/zzzeek/sqlalchemy/pull/369, a user is getting blank for "SHOW VARIABLES LIKE 'sql_mode'" and I think this might be what's happening. The MySQL logic needs to be ready for no row returned here and it should emit a warning.

Comments (2)

  1. Mike Bayer reporter

    Handle SHOW VARIABLES returning no row

    MySQL 5.7 has introduced permission limiting for the "SHOW VARIABLES" command; the MySQL dialect will now handle when SHOW returns no row, in particular for the initial fetch of SQL_MODE, and will emit a warning that user permissions should be modified to allow the row to be present.

    Change-Id: I98e7a69230da397b17eae07b7e9d024fa7aeeb26 Fixes: #4007

    → <<cset 5650a0c30639>>

  2. Mike Bayer reporter

    Handle SHOW VARIABLES returning no row

    MySQL 5.7 has introduced permission limiting for the "SHOW VARIABLES" command; the MySQL dialect will now handle when SHOW returns no row, in particular for the initial fetch of SQL_MODE, and will emit a warning that user permissions should be modified to allow the row to be present.

    Change-Id: I98e7a69230da397b17eae07b7e9d024fa7aeeb26 Fixes: #4007 (cherry picked from commit 5650a0c306391216a9c9ce1961c5b548e534b5eb)

    → <<cset 94a0ed697a12>>

  3. Log in to comment