Quote:
Originally Posted by danblack
(Post 6215414)
I'm struggling to understand how defaults relate to migration (sql_mode?). Do you have time to provide me with more details? Which source databases do you consider here?
|
1. On windows file names are case insensative and tables are created the way the user used capitalisation on typing the "create table" SQL command. I've seen more than once that migration to file systems that are not case insensative will FAIL on the ANSI standard the typing table names in SQL commands is ought to be case insensative does not work. Likewise for compiled programs that use all lowercase vs all uppercase in SQL commands.
2. The default installation for mysql was (and I fear still is) prohibits spaces on places that will make end users curse: "select count (*) from foo;" is (was) not allowed in a default installation. (a space between count and (*)). This is for all functions.
So I need to add two lines to /etc/my.cnf to be able to work with MySQL/MariaDB at all
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES,IGNORE_SPACE
lower_case_table_names=1
Easy on my own boxes, but not on servers or other peoples boxes
Quote:
Originally Posted by danblack
(Post 6215414)
If dbeaver (feature request 10070) exposed the roles functionality that has been there since 10.0.5 would this be acceptable?
Other notable user-management options that have existed for a while, that can easily get missed are: account locking was added in 10.4.2 and password expiry in 10.4.3. The SUPER privilege was split up in 10.5.2.
With these it looks almost comparable to Postgres in terms of user management features. Or have I missed a key feature that still is required?
|
I *LOVE* DBeaver! It takes away most of my user-management issues for MySQL and Oracle.
Thanks for the extra links, I'm going to store them in my mysql notes
|