We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submitted by: pablo santos (psantosl)
On FbDataReader.cs, line ~377: for (int i = 0; i < this.fields.Count; i++) { columnsIndexes.Add(this.fields[i].Alias.ToUpper(), i); }
The error shows up when trying to run a sql like: select table1.field, table2.field
On such cases fields[i].Alias is "field" for both items. This causes the dictionary columnsIndexes to throw the "duplicate key" error.
Maybe a solution is to concatenate Alias and Relation? columnsIndexes.Add(this.fields[i].Relation.ToUpper() +"."+this.fields[i].Alias.ToUpper(), i);
As a side note, ToUpper() can be removed if columnsIndexes is instantiated using StringComparer.CurrentCultureIgnoreCase.
Commits: 3e1861e
The text was updated successfully, but these errors were encountered:
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 2.5.1 [ 10360 ]
Sorry, something went wrong.
cincuranet
No branches or pull requests
Submitted by: pablo santos (psantosl)
On FbDataReader.cs, line ~377:
for (int i = 0; i < this.fields.Count; i++)
{
columnsIndexes.Add(this.fields[i].Alias.ToUpper(), i);
}
The error shows up when trying to run a sql like:
select table1.field, table2.field
On such cases fields[i].Alias is "field" for both items. This causes
the dictionary columnsIndexes to throw the "duplicate key" error.
Maybe a solution is to concatenate Alias and Relation?
columnsIndexes.Add(this.fields[i].Relation.ToUpper()
+"."+this.fields[i].Alias.ToUpper(), i);
As a side note, ToUpper() can be removed if columnsIndexes is
instantiated using StringComparer.CurrentCultureIgnoreCase.
Commits: 3e1861e
The text was updated successfully, but these errors were encountered: