-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cnf priority #97
Comments
Which code line are we talking about? This is unfortunately still being handled in a couple places. In general, I'm trying to sketch out the preferred order here, which is a longer list than this one: just 'global general cnf', for example, comes out at:
The order of this list has to depend on what privileges the server is requesting. So a query should ask for read-only permissions first and then fall back to an account that allows it to write; while a creation scheme script should ask for administrative user first, fall back to a root user, and finally fall back to a read-only account (b/c there still might be something they can do). |
I made some config changes (i.e. adding os.path.expanduser to home paths), only to git pull and see that they were already done! That's why you pull to start. I have one discussion topic though, regarding the priority order.
Currently, the order is 1) local user locations (~/.my.cnf), then 2) global mysql locations (/etc/mysql/my.cnf), then finally 3) a local directory file that can overwrite everything. It seems to me that the sensible order would be to reverse (1) and (2), and add /etc/bookworm/my.cnf right before (3).
This is what I would suggest, which is global general cnf, local general cnf, global bookworm-specific cnf, local bookworm-specific cnf:
The text was updated successfully, but these errors were encountered: