Our current SQL aliasing always just takes the first character of the identifier, so Order and OrderItems both get [o]; this causes uniquification to kick in, and we end up with o and o0 which are pretty hard to distinguish when looking at the SQL.
We could identify the pascal-cased .NET name and generate wider aliases, e.g. [o] and [oi]; this would improve our SQL readability/cleanliness.
Note that we'd probably want to support other naming schemes, e.g. snake_case.
Our current SQL aliasing always just takes the first character of the identifier, so Order and OrderItems both get
[o]; this causes uniquification to kick in, and we end up withoando0which are pretty hard to distinguish when looking at the SQL.We could identify the pascal-cased .NET name and generate wider aliases, e.g.
[o]and[oi]; this would improve our SQL readability/cleanliness.Note that we'd probably want to support other naming schemes, e.g. snake_case.