What's new with BroadSQL 5.1.3 (2026-09-05)

New features

• New JS command family: JS RUN <file> [args...] runs a saved .js script, JS EVAL <code> runs a one-line snippet typed directly on the command line. A script can call connect(name) to open one or more independent database connections at once (something the interactive shell cannot do, since CONNECT always closes whatever was open before), or use db to reuse whichever connection is already active. <connection>.execute(sql)/.executeUpdate(sql) run queries, print/println write to the console. JS LIST/JS FIND catalog .js files (their own JsScripts folder, new BroadSQL.ini key) the same way SCRIPT LIST/SCRIPT FIND do, including the same -- @description/@instance/@environment/@tags/@alias/@status metadata header. No sandbox: a script runs at the same trust level as an extension JAR. See Light scripting with JS.

Problems solved

• Instance and Environment values were swapped: every connection's Instance field (shown by SHOW CONNECTION/SHOW ALL CONNECTIONS and the CONFIG screen) actually held a deployment-stage value (DEV, QA, PROD...) and its Environment field a product/application name, the opposite of what those two fields mean. A new one-time command, FIX INSTANCE ENVIRONMENT SWAP, corrects this for an existing Connections Definition File: it backs up the file first, then swaps the two fields for every connection so Instance finally holds the product/application name and Environment the deployment stage. Run it once; running it a second time on an already-corrected file swaps the data back, so there is no automatic detection of whether it has already been applied. See FIX INSTANCE ENVIRONMENT SWAP.
• The CONFIG screen's "Instances" tab (add/rename/deactivate) now actually manages the Instance list used by the Connection form's Instance field: it was silently managing the Environment list instead.
• SHOW INSTANCES replaced by SHOW ENVIRONMENTS: the old command fixed the current connection's Environment and listed every connection sharing it across every Instance, the wrong direction once Instance/Environment hold their correct meaning (see above). SHOW ENVIRONMENTS [connectionId] [environmentName] (aliases SH ENV, SHENV, SHOW ENVTS) fixes the connection's Instance instead and lists every Environment within it, e.g. SHOW ENVIRONMENTS DESK lists every connection belonging to the DESK instance, one row per environment. SHOW INSTANCES is gone, not kept as an alias. See SHOW ENVIRONMENTS.

Installing BroadSQL 5.1.3

See Installation.

Upgrading from previous releases

No special steps required for this release.

Known issues

None known at release time.