[C#] Column names should be case sensitive #33970
Comments
DanTm99
changed the title
DanTm99
added a commit
to DanTm99/arrow
that referenced
this issue
Feb 6, 2023
…field-names-case-sensitive
eerhardt
pushed a commit
that referenced
this issue
Feb 6, 2023
Remove the use of a comparer that ignores casing when building the fields dictionary for a schema. This allows for fields with names that differ only in casing. Currently, fields with names that only differ in casing will be seen as having the same name and will cause an Exception to be thrown due to being seen as having duplicate keys. * Closes: #33970 Authored-by: Danyaal Khan <danyaal99@hotmail.co.uk> Signed-off-by: Eric Erhardt <eric.erhardt@microsoft.com>
sjperkins
pushed a commit
to sjperkins/arrow
that referenced
this issue
Feb 10, 2023
…3978) Remove the use of a comparer that ignores casing when building the fields dictionary for a schema. This allows for fields with names that differ only in casing. Currently, fields with names that only differ in casing will be seen as having the same name and will cause an Exception to be thrown due to being seen as having duplicate keys. * Closes: apache#33970 Authored-by: Danyaal Khan <danyaal99@hotmail.co.uk> Signed-off-by: Eric Erhardt <eric.erhardt@microsoft.com>
gringasalpastor
pushed a commit
to gringasalpastor/arrow
that referenced
this issue
Feb 17, 2023
…3978) Remove the use of a comparer that ignores casing when building the fields dictionary for a schema. This allows for fields with names that differ only in casing. Currently, fields with names that only differ in casing will be seen as having the same name and will cause an Exception to be thrown due to being seen as having duplicate keys. * Closes: apache#33970 Authored-by: Danyaal Khan <danyaal99@hotmail.co.uk> Signed-off-by: Eric Erhardt <eric.erhardt@microsoft.com>
fatemehp
pushed a commit
to fatemehp/arrow
that referenced
this issue
Feb 24, 2023
…3978) Remove the use of a comparer that ignores casing when building the fields dictionary for a schema. This allows for fields with names that differ only in casing. Currently, fields with names that only differ in casing will be seen as having the same name and will cause an Exception to be thrown due to being seen as having duplicate keys. * Closes: apache#33970 Authored-by: Danyaal Khan <danyaal99@hotmail.co.uk> Signed-off-by: Eric Erhardt <eric.erhardt@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
In the Schema constructor in Schema.cs, the casing of field names is ignored when constructing the
_fieldsDictionary(by usingStringComparer.OrdinalIgnoreCasewhen constructing the dictionary).This disallows multiple fields whose name only differs in casing, even though it should be allowed.
Component(s)
C#
The text was updated successfully, but these errors were encountered: