Note on verbiage: I chose "Everybody" rather than "Everyone" or "Fallback" as the pretty name for this account.
"Fallback" just seemed like it was misplaced in the user dropdown list.
"Everyone" seems to mean individuals in a group, while "everybody" seems to mean the group as a whole. Thus "everyone" is a bit more personal.
This could convey the notion that you need to have a personal account before these privileges will apply to you, which is not the case. Anyone that logs in with a non-existent user name will get these privileges.
Therefore, "Everybody". It hopefully denotes that the privileges are given to everyone with a personal account, PLUS people authenticating with a rubbish user name (and the password, if any).
This last category of logins are commonly called "anonymous users" in the MySQL documentation. "Anonymous" does not quite fit this account however, because the privileges given also apply to everyone else.
* Bugfix: Copy + paste same text in the username field caused a warning.
- Accounts and existing privileges are presented in a pulldown which makes it as easy to use as a toy
- Adding privileges calls the new SelectDBO dialog which is basically a tree like childwins dbtree
- Updating accounts canonicalizes various odd/legacy mechanisms in the MySQL user system
- Fullfills feature request #1547437 (btw)
- Wants to be tested heavily on different servers
A result of a team work. 1000 thanks to rosenfield for the admin friendly logic implementation, tons of fixes and usability ideas.
- Consequently use Mainform.GetRegValue() to read these values, an overloaded method with either Boolean, String or Integer result. These methods keep a global TRegistry object (regMain) open while the application runs, rather than creating a new one for each caller.
- Remove Mainform.SaveRegValue() which was used in one or two callers. Rather use a TRegistry object and do that by hand. There's no significant advantage in using a SaveRegValue method currently.
