New issue
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
Area names containing Unicode characters are corrupted (SQL Server only) #79
Comments
Isn't this front-end development? If the values are OK in both databases, and Windows is getting code page 1252, isn't that the problem? If we set the pages to be UTF-8, it should just work. I'd be interested to see what I get on Mac. What would I need to do to see the relevant data? |
Some examples from the US geography in Puerto Rico:
Postgres (correct):
SQL Server (wrong):
|
Maybe an obvious question, but did you change the column type with the data in place? And if so, is the result any different if you insert the data after the column is I recall seeing things like this with multiple languages, and if you changed the data type after the data was in, it didn't always do what you hoped. |
The columns are all NVARCHAR(1000) all the way back to the initial load table. They indicates an issue with BULK INSERT the SQL Server load command Use Unicode Character Format to Import or Export Data:
|
Fix by pull #152 Support Unicode in SQL Server BULK INSERT statements. |
E.g. Slättåkra-Kvibille is corrupted
The text was updated successfully, but these errors were encountered: