You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is because in our reader column logic, we assume column names are case-insensitive; SQL Server indeed does not allow creating a table with two columns that differ from one another only by case, but this isn't true of other databases (e.g. PostgreSQL, possibly SQLite).
Unfortunately, change the logic to be case-sensitive would break any users currently using SQL Server and using names that match only case-insensitively; that would be too much. However, we can allow providers to specify whether they want case-sensitive or insensitive behavior.
Given the following entity type:
The following query works:
This is because in our reader column logic, we assume column names are case-insensitive; SQL Server indeed does not allow creating a table with two columns that differ from one another only by case, but this isn't true of other databases (e.g. PostgreSQL, possibly SQLite).
Unfortunately, change the logic to be case-sensitive would break any users currently using SQL Server and using names that match only case-insensitively; that would be too much. However, we can allow providers to specify whether they want case-sensitive or insensitive behavior.
Originally flagged by @simonmckenzie in #33748
The text was updated successfully, but these errors were encountered: