When bx-mssql is installed/loaded into boxlang core AND a single datasource is constructed using the mssql driver, all subsequent datasource creations error due to an invalid connection string.

Upon closer inspection, it appears that the bx-mssql DB driver is setting a trustServerCertificate: true custom parameter into shared state in the DatasourceConfig.DEFAULTS public static final property, which then applies that custom parameter to every datasource created thereafter.

See screenshot - in this case, the datasource creation is attempting to append ?trustServerCertificate=true to a Derby datasource connection string. Neither the parameter nor the ? URI delimiter is appropriate in this case. (Though the URI delimiter would be resolved by installing bx-derby, we shouldn’t need to require the bx-derby module just to avoid mutating a valid connection string.)