Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Sharjeel
Starting Member
8 Posts |
Posted - 2003-06-09 : 07:02:20
|
| My web based application(asp) uses Thai interface to save Thai data in SQL Server 2000 database.I noticed that the thai characters are getting saved in the form of hash codes eg.& #3629;& #3637;& #3648;& #3617;& #3621;& #3660;So,is there a way to save the data as actual Thai cahracters instead of the hash code in SQL server 2000 ?Thanx.SharjeelServer ManagerMega E-Services.com |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2003-06-09 : 07:11:18
|
| There's some discussion about this in the thread[url]http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=26051[/url]Near the very bottom of the thread, there's a post from Arnold which clarified that the DB will always hold 2-byte UTF-16 characters but ADO/ASP will convert them automatically to UTF-8 (or whatever the codepage is set to - more on that earlier in the thread).Sam |
 |
|
|
Arnold Fribble
Yak-finder General
1961 Posts |
Posted - 2003-06-09 : 08:35:53
|
| I think what he's saying is that they're getting stored as XML character references -- i.e. the character with unicode U+0E2D (Thai Character O Ang) is getting stored as the 7 ASCII character sequence & # 3 6 2 9 ;(sorry, I don't really have any suggestions for fixing it -- perhaps the application code thinks it is attempting to encode XML in a character set that doesn't support Thai characters)Edited by - Arnold Fribble on 06/09/2003 08:39:17 |
 |
|
|
|
|
|