You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current escaping setup is designed to work with table name formats such as "scheme.table_name" and it will try to automatically escape table names on "." separator.
When working with names as "dbo.[something.something]" the existing escaping setup fails due to the fact that it is assumed that every . is a break in the name.
Dapper and other ADO.net components do not auto-escape names, probably due to such scenarios, and it is expected that the designer of the model escapes them himself in the Table and Column attributes.
I see two fixes for this
Remove auto-escaping
Did it in a fork & can create a pull request to merge it in, but this will be a breaking change to anyone not escaping names properly already.
Change parsing
Change the parsing of the table name to ignore everything that is already escaped, ie. between [ ] within the supplied name. In the next couple of days I can make the change in this direction if that would be more desirable.
The text was updated successfully, but these errors were encountered:
The current escaping setup is designed to work with table name formats such as "scheme.table_name" and it will try to automatically escape table names on "." separator.
When working with names as "dbo.[something.something]" the existing escaping setup fails due to the fact that it is assumed that every . is a break in the name.
Dapper and other ADO.net components do not auto-escape names, probably due to such scenarios, and it is expected that the designer of the model escapes them himself in the Table and Column attributes.
I see two fixes for this
Remove auto-escaping
Did it in a fork & can create a pull request to merge it in, but this will be a breaking change to anyone not escaping names properly already.
Change parsing
Change the parsing of the table name to ignore everything that is already escaped, ie. between [ ] within the supplied name. In the next couple of days I can make the change in this direction if that would be more desirable.
The text was updated successfully, but these errors were encountered: