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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2001-08-29 : 18:53:01
|
| Apoorv Durga writes "I have an SQL Server 7 databse with default encoding and i'm trying to stote multilingual content in it. Let's say i've defined a table called Article which has a field called body of datatype varchar. When i store a multilingual content (say Hindi, malayalam or Chinese), theoritically i should not be able to do so because the datatype should be nvarchar and not varchar. Howeve, i'm using servlets and jsp to insert hindi content and what happens is that the hindi characters (or chinese for that matter) are being stored as equivalent decimal characters. As an example, the Malayalam content is stored as equivalent decimal reprecentation (e.g.,ഈ which is a decimal representation of a particular Malayalam character). Similarly, other Malayalam characters are stored as their respective decimal equivalents. Although content can be viewed properly but it is actually stored as a decimal number and not Malayalam character. When i try to view it i can see it perfectly.So my question is: If i can use the default encoding to store these characters, why do i need Unicode at all??" |
|
|
|
|
|