SchemaUpdateTest fails on databases using case-insensitive identifiers
Description
SchemaUpdateTest is explicitly skipped for SQL Server on master.
I am adding a check for case-insensitive quoted identifiers to the test that will work to skip the test on database that store case-insensitive identifiers as lower-case or upper-case. It will not work for databases that store case-insensitive identifiers as mixed-case (like SQL Server).
Those databases that store case-insensitive identifiers in mixed-case will need to be skipped explicitly, like is already done for SQL Server.
I've pushed a fix with the added check. I've confirmed it worked to (correctly) skip the test on MariaDB. I'll leave this open in case there are still failures on other databases.
SchemaUpdateTest is explicitly skipped for SQL Server on master.
I am adding a check for case-insensitive quoted identifiers to the test that will work to skip the test on database that store case-insensitive identifiers as lower-case or upper-case. It will not work for databases that store case-insensitive identifiers as mixed-case (like SQL Server).
Those databases that store case-insensitive identifiers in mixed-case will need to be skipped explicitly, like is already done for SQL Server.