SQL: Storing Extended ASCII (128 to 255) in VARCHAR

≯℡__Kan透↙ 提交于 2019-12-24 09:47:29

问题


How do you store chars 128 to 255 in VARCHAR..?

SQL seems to change some of these to char(63) '?'. I'm not sure if it's something to do with collation? UTF-8? N'..'? I've tried COLLATE Latin1_General_Bin, not sure if it supports extended ascii though..

Obviously works with NVARCHAR, but in theory this should work in VARCHAR too..?


回答1:


The character stored in varchar/char columns beyond the ASCII 0-127 character range is determined by the code page associated with the collation. Characters not specifically defined by the code page are ether mapped to a similar character or, when there is none, '?'.

You can list collations along with the associated code page with this query:

SELECT name, description, COLLATIONPROPERTY(name, 'CodePage') AS CodePage
FROM fn_helpcollations();



回答2:


Dan's answer got me on the write track.

VARCHAR definitely does store Extended ASCII, but it depends on the code page associated with the collation. I'm using Latin1_General_100_BIN which uses code page 1252.

https://en.wikipedia.org/wiki/Windows-1252

According to this code page the the following chars are undefined:

129, 141, 143, 144, 157

In reality it looks like SQL exclude most chars from 128 to 159. Easy solution was just to remove those characters.



来源:https://stackoverflow.com/questions/44344747/sql-storing-extended-ascii-128-to-255-in-varchar

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!