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
I have found the problem! Parser uses Regex with IgnoreCase option. This likely changes source string character case to upper. But the system language setting is Turkish and the upper case 'i' in Turkish is not 'I', it is 'İ' (I with a dot over it). So 'index' can not be matched. Other keywords which contains 'i' character also can not be matched.
In order to avoid this situation CultureInvariant option could be used but in this case non ASCII characters used in SQL object names possibly will not be matched.
I shall circumvent this using upper case keywords this time and return this problem later. May be I shall manage to suggest something. Nothing to fix on your side for the time being.
Thank you for this excellent migration tool by the way.
@mozsoyler Nice find. It's still a bug though, because DDL syntax (i.e: "CREATE INDEX") will always be in English, so it should be matched with the invariant culture as you suggested
I want to create an index on a table in a schema as follows:
But this line causes Insight.Database.Schema.SchemaParsingException to be thrown with the message: Cannot determine the type of the SQL script.
When i comment out this line all works ok.
How can I create an index using Insight.Database.Schema?
The text was updated successfully, but these errors were encountered: