|
The '≥' is not representable in code page 1251 or 1252 therefore it was replaced with a substitution character when you inserted it. You can peruse the character sets here: http://demo.icu-project.org/icu-bin/convexp. Specifically, windows-1251 is here: http://demo.icu-project.org/icu-bin/convexp?conv=ibm-5347_P100-1998&s=ALL and windows-1252 is here: http://demo.icu-project.org/icu-bin/convexp?conv=ibm-5348_P100-1997&s=ALL -john. |
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 28 Nov '12, 11:03
question was seen: 2,092 times
last updated: 29 Nov '12, 13:24
Can you give us some more details to your question: what SA and ISQL version are you using, in which context (OS, language) and what are you trying to do (e.g. SQL statement)?
I have a column and stored a ≥ character, but it displays a square, instead of ≥ in the ISQL. The version I am using is v12.
What database collation & charset is being used? How was the data inserted?
It could also be a font issue. If the font you're using doesn't have an entry for the character, it will typically display it as a box. What OS are you using?
Can the SQL Statements area show the character correctly? Or is it just messed up in the results view?
The Collation is 1251LATIN1, Charset is windows-1252. I pasted the character into the field. I am using Windows XP.
So, what should I do?
If you want to store that character, you need to use a character set & collation that supports it. The UTF8BIN and UCA collations both support the UTF-8 character set that can encode all of Unicode. To change your database collation, you must unload your database, create a new one with the correct collation and then reload the data.
Also note that on your OS that uses windows-1252, only Unicode applications will be able to display the character. So dbisql will be able to show it but dbisqlc will not. Non-unicode apps on Windows can only deal with the OS charset.