Install
Works with Drupal: 7.xUsing Composer to manage Drupal site dependencies
Downloads
Download tar.gz
21.25 KB
MD5: ed5726f53c0d2567099ab70f70eaaad0
SHA-1: a8f093631cfab47e9bd9354bbd6f81ee39de10b2
SHA-256: b6a09701417ada932db07ecb6769bd2cd8786f8a0dd9d2d29f8d0dfb606c100c
Download zip
25.13 KB
MD5: 8059f62b0a2d6a5996da637a513aed02
SHA-1: bd35bf187b09c3ff652557a068335bb15da600f3
SHA-256: 84685d57513ebc9bb4a29eeceb43ccef0daa3760d4add0caa6e6fbd176734509
Release notes
Second release candidate for the SQL Server driver for Drupal 7. Now with experimental support for SQL Azure, the cloud version of SQL Server.
Note that updated installation instructions can be found on the project page.
Changes since 7.x-1.0-rc1:
- Rename the database folder to make installation easier.
- Try querying the schema one table at a time to avoid deadlocks.
- Replace the use of the information schema with direct system catalog queries.
- Implement technical primary keys for Azure.
- Add basic tests for primary key handling.
- Move the database files to a separate directory and implement a simple support module.
- Use a direct query to the table in fieldExists() instead of querying the system catalogs to try to reduce lock contention during testing.
- Fix for 'The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless TOP or FOR XML is also specified.'
- Properly count affected rows, not matched rows to comply to Drupal standards.
- #1027952: expand GROUP BY aliases.
- Workaround Azure obvious limitations.
- Use the new watchdog_exception() now.
- #1050798 by myself: properly rename all the table objects (including primary keys) when we rename a table.
- #1050800 by myself: Workaround SQL Server casting weirdness that make unique index only consider the first 16 characters.