Stonie/Sprocker — Issue #1: Address case sensitivity problems
Author: Stonie
Created: 2012-01-16 23:24:04+00:00
State: open

Since parameter mappers and row mappers use reflection to map parameter names and result set field names to CLR properties, case sensitivity is important.

Using a camel-case parameter name or result set field name, although case-insensitive in SQL, will result in a failure to map to the equivalent Pascal-cased C# class property.

Maintaining this case-sensitivity for mapping resolution is important. It is valid for a C# class to define properties that differ only by case (even by accident) e.g. Id vs ID. If the mapper was case-insensitive, there would be the potential for non-deterministic mapping resolution depending on whether the parameter or result set field is named [Id] or [ID] respectively.

* VS2010 Database Projects will not detect and hence not deploy a change if ONLY CAPITALISATION of stored procedure parameters, etc. differs.