All sql server extraction queries should use correct case characters for catalog tables. This is very important in the case that the collation is set to a case sensitive collation.
Example: following will through an invalid object for information_schema.constraint_column_usage table when collation is case sensitive
// case-sensitive ALTER DATABASE "Chinook" COLLATE Latin1_General_Bin GO USE "Chinook" GO select count (*) from information_schema.constraint_column_usage GO select count (*) from INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE GO // case-insensitive ALTER DATABASE "Chinook" COLLATE SQL_Latin1_General_CP1_CI_AS GO USE "Chinook" GO select count (*) from information_schema.constraint_column_usage GO select count (*) from INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE GO
After searching through extraction code, we found that the incorrect casing was used for INFORMATION_SCHEMA catalog tables in 3 places:
1.) SQL Azure, constrains node... fixed...
2.) SQL Server, constraints extraction query... fixed...
3.) SQL Server, Object search, sequences extraction
Committed revision: 53681
Issue #15100 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build v18.0.5-11 |
No time estimate |
After searching through extraction code, we found that the incorrect casing was used for INFORMATION_SCHEMA catalog tables in 3 places:
1.) SQL Azure, constrains node... fixed...
2.) SQL Server, constraints extraction query... fixed...
3.) SQL Server, Object search, sequences extraction
Committed revision: 53681