.NET Libraries / Case Sensitive Object Names with SQL Server

ServiceSoftware

I'm running into errors due to case sensitivity of table names, field names, etc. Ran into this especially with a LeftJoin. I've taken to using .ToLowerCase in all our code-generated JavaScript and code-generated controllers (the controller is where we hit the issue).

The question is whether case-sensitivity in table, field, and other names in .NET Libraries is intentional? When using SQL Server the use of case-insensitive code pages is typical.

allan

Yes - it is intentionally case sensitive. Javascript script itself is case sensitive and Editor follows that path. For example if you were to specify new Field("Table.Field") then on the Javascript you have to know the case for how to access the data for that field. It would be valid to transform to a common case, but case insensitive access to the object's data would add significant overhead to the access in Javascript. So the approach taken is to use the original case.

Regards,
Allan