Standardize permissions and executions on MySQL schemata: Char %60 (`)
See original GitHub issueCurrent permissions on MySQL schemata do not include character %60 (`) but SuperSet uses such character in the Preview option of SQL Lab. Therefore even if a user has access to a schema the preview option will fail due to permissions.
Bug present on SuperSet 1.1.0 installed from PyPi
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
13.4.2.1 CHANGE MASTER TO Statement
Before MySQL 8.0.17 it was 60 characters. If you specify MASTER_HOST or MASTER_PORT , the replica assumes that the source server is different...
Read more >MySQL 8.0 Reference Manual :: 13.7.1.6 GRANT Statement
The GRANT statement assigns privileges and roles to MySQL user accounts and ... GRANT supports host names up to 255 characters long (60...
Read more >6.2.2 Privileges Provided by MySQL
The PROCESS privilege controls access to information about threads executing within the server (that is, information about statements being executed by sessions) ...
Read more >Chapter 4, Optimizing Schema and Data Types - O'Reilly
Since MySQL 4.1, each string column can have its own character set and set of sorting rules for that character set, or collation...
Read more >MySQL 5.6 Reference Manual - Oracle Help Center
4.6.13 mysql_fix_extensions — Normalize Table File Name Extensions . ... 4.6.14 mysql_setpermission — Interactively Set Permissions in Grant ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@qlands I was able to reproduce, possible bug
It seems we’re using sqlparse 0.4.3, so I’m going to optimistically close this as resolved. If anyone still sees an issue (particularly in Superset > 1.5.2), I’m more than happy to re-open this and get more eyes on it!