v1.3.19

What's new in 1.3.19

A user editor. Users has grown from a list of grants into the place accounts are looked after.

• Privileges... shows what an account or role may do - on the whole server, one database or one table - as boxes, ticked for what it has. Changing them shows the GRANT and REVOKE they become before anything runs. The boxes are the server's own list, so a privilege only MySQL or only MariaDB has shows where it exists. Typing a GRANT or REVOKE by hand is still there, for columns and routines.
• Roles. New > Create role, and Roles... to give an account roles and pick the one active when it signs in - on MySQL and MariaDB alike, though the two keep roles differently.
• Clone makes a new account like the selected one: its sign-in method, settings, grants and roles, under its own name, host and password.
• Account > Settings... - and Create user - set the sign-in method, SSL required or a client certificate, password expiry and the four connection limits. Only what changed is sent, and a password never reaches the log. Lock and Unlock are in the same menu.
• The list has a filter and marks each entry as a role, a system account, locked or password expired; the selected account's details sit over its grants. Who has access... lists everyone with privileges on a database, down to its tables and columns.
• The buttons fit in one row: what acts on the selected account stays grey until there is one.

Export: structure only, or data only. Export asks first what goes in - structure and data, structure only, or data only. Data only leaves out routines, events, triggers and the CREATE and DROP lines, and still writes a file per table. It opens at structure and data every time, so a backup never goes out without its rows because of an earlier choice. The options most exports change stay on show under plain names; the rest fold into Advanced options, each with its mysqldump option in its tooltip.

Import lists its files with their folder and size, each with its own remove button, instead of a box of typed paths. A file added twice is listed once, and the target database offers the server's databases in both editions.

The user transfer script is sound.

• It carries roles: on MariaDB they were lost, with every grant that named them; on MySQL an account with a default role could come before its role and fail.
• It can run again on a server that already has some of the accounts.
• Its first line stops it on the wrong kind of server - a MySQL script on MariaDB or the other way round - before anything is changed.

Smaller things.

• When the query bar is narrow, Run Selection and Explain keep their labels longest; Chart sits with Copy, Wrap and Columns, left of the search box.
• The eye in a password box is centred on it.
• Menus and the database list draw above floating windows however often those have been raised.

Verify your download

These installers are not code-signed. Compare what you downloaded against the SHA-256 below:

85e0e21361b7ffa8f3f4e4ca0fd34873ec0c7c4fb87a94b6d44c92850d4f6737  NOBS.SQL.Editor_1.3.19_x64-setup.exe
1fbde86b1a33922f6ce9131069c1e8f9614d1fbe62ee571cff71572361f610d1  NOBS.SQL.Editor_1.3.19_x64_en-US.msi

PowerShell: Get-FileHash .\<file> -Algorithm SHA256

See CODE_SIGNING.md for what this does and does not prove.

Full Changelog: v1.3.18...v1.3.19