Because database drivers are not really first-class citizens in Drupal, they cannot receive security updates. We need to build an helper module that will be auto-enabled.

This module:

- will be installed in the modules directory, includes/database/sqlsrv being a symlink (aka junction point) to the module
- will auto-enable itself when SQLSrv is the default database connection
- will allow us to implement SQLSrv-specific test cases

Comments

damien tournoud’s picture

damien tournoud commented

The mklink tool seems to be able to create symbolic links on Windows.

david_garcia’s picture

david_garcia commented
Version: 7.x-1.x-dev » 8.x-1.x-dev
Issue summary: View changes

The D8 version already has a full featured module (based on the D7 version) that provides some driver settings check in the sites report page, and provides a set of driver specific tests.

I am not so sure about the symlink strategy to keep in sync the driver and the module. Maybe it is simpler and more problem proof to hardcore a version control number in both the module and the driver, and if these numbers are differente output a warning in the site report page. This way, people will be aware that they need to update the driver when the module is automatically updated.

david_garcia’s picture

david_garcia commented
Status: Active » Closed (fixed)

I think this is the best that can be done with little risk: show a warning in the status page if the driver in the module directory is different from the one effectively deployed in the website.

So updates still require end user intervention but at least they know that something is out of sync.