I need to be able to save Chinese chars in my active database with ColdFusion 9
I have already figured out how to do it set the field types to NVARCHARS and NTEXT.
I have checked off Enable High ASCII characters and Unicode for data sources configured for non-Latin characters under the Datasources section.
It works great but... here is the question.
Changing the option Enable High ASCII characters and Unicode for data sources configured for non-Latin characters - will this create any other downstream issue with the current application? We will need to update the database structure - I am not sure what effect this option will have to my legacy code.
That should not have any effect on your database or your code. It's just a setting on how the application server (coldfusion) communicates to your database server.
Related
I'm using Tableau Rest API to retrieve the list of workbooks from Tableau Server and show the list on a webpage. The problem is that special characters in workbook names have invalid encoding (or at least encoding that I do not expect).
Name set in Tableau server web UI:
Book ó
Name retrieved from rest API:
Book ó
As far as I can tell this issue occured after we upgraded Tableau server to 2018.1.
Is there a way to specify the encoding in Tableau Rest API? Or determine the encoding used to store the workbook name in Tableau Server web UI?
Turns out that after Tableau Server was updated to 2018.1 C# WebClient needs to have encoding set explicitly to UTF8 to handle special characters properly when querying Tableau REST API.
I have a problem..
I work with ASP.NET and After I add a data (Arabic language) to my form via the browser it added to the SQL Server Management Studio like this (???????) even when I retrieve the data entered by the browser, Although there is no problem when I add my Arabic data via SQL Server Management Studio direct.
(there is no problem with English data)
Somewhere along the way your changing the charactertype to something else, that is probably Standart ascii.
It is impossible to know where exactly since we don't have hany information about that, but I would guess that in your Backend things are messed up, try commenting out your code and just echoing the values to see if they are already wrong at that stage.
Maybe change the Stringtype to utf-16
That should support any chars you throw at it
I opened up a Northwind database (northwind.sqlite3) using DB Browser for SQLite (Version 3.9.1).
For some product names, I couldn't get the right names displayed no matter what I did, including:
I changed new line characters options
I changed Preferences options
I checked the outputted csv using Excel and Notepad with different encoding
Still couldn't figure out how to properly show the characters...Any help is appreciated.
The problem may be either that data have been added to the database in an incompatible encoding (e.g., pasting data from Microsoft products into a UTF-8 database can do this) or that the DB Browser isn't displaying the data in the correct encoding. To fix the former problem you may have to edit the data, or possibly change the database encoding. You can't change the encoding of a SQLite database on the fly, so you would have to export the data and import them into a new database with the encoding that is actually used. If it's just a DB Browser display issue, right-click on the table header and choose the option to change the display encoding.
I have a new server with the same Classic ASP code connecting to same SQL Server 2000 database with the same connection string yet it seems to be pulling data out of the database differently now. Specifically there is a custom encryption function which creates special characters (non-ASCII) and stores them in a VARCHAR field. (This is legacy code.) Since nothing has changed except the web server it has been hard to diagnose this problem.
Is there some setting that would control the database driver which would allow this data to come out of the database? It seems the character set is not treated the same with the new server as it was with the old server. Is there something I can change in the ODBC driver settings?
The server version change is from IIS 6 to IIS 7.5. The new server obviously also has new ODBC driver versions.
Any help is appreciated?
I suspect something to do with Locale rather than anything else. However I don't understand Locale. :-(
If it is a stored proc, a quick-fix might be to change the data type on the DB parameter/column to NVARCHAR. With ASP it will be unicode BSTR values in the application anyway, so moving the conversion into the database may make it easier to control, if necessary by specifying a collation to use for the conversion.
If you have the ASP code you could also edit the select to say cast(password as nvarchar(50)) as password or whatever to achieve the same result.
How do you set the character encoding being used by the web server?
Thanks, R.
We found out what was causing the problem. The style sheet had become corrupted with some eroneous characters being written to the front of the file. The server was misinterpreting them causing it to change the encoding type that it was using. Deleted these chars and it worked great.