SA 7.4.435 Unicode support

SA 7.4.435 Unicode support

When do you plan to support for Unicode in the code and the data is displayed?

For example, when trying to see the code of the function foo() message is displayed:

Code:

/*
Cannot find source code for "foo".
DDL utility returned error:
Execute: ODBC Error (7): SQLExecDirect
Client: 09.03.0400
Server: 9.4.5
SQL State: 22P05
ERROR: character with byte sequence 0xc3 0xbc in encoding "UTF8" has no equivalent in encoding "WIN1251";
Error while executing the query;

select 'CREATE VIEW "' || table_schema || '"."' || table_name || '" AS' || chr(10) || view_definition
from information_schema.views
where
table_schema = ?
and table_name = ?

UNION ALL

SELECT
'CREATE FUNCTION "' || routine_schema || '"."' || routine_name || '"(' ||
array_to_string(array(
SELECT COALESCE (p.parameter_name, '') || ' ' || LOWER (p.parameter_mode) || ' ' || REPLACE (p.data_type, '"', '')
FROM information_schema.parameters p

... and so on (cuted)

*/

Also when i try to quick view (by Ctrl+click) any table with Unicode, error appears:

	Code:
	Code 7, State 22P05, ERROR: character with byte sequence 0xf0 0x9f 0x98 0x8d in encoding "UTF8" has no equivalent in encoding "WIN1251"; Error while executing the query The command(s) completed with errors (66.16 ms).

It concerns, for example, Deutsche umlaute (ä, ö, ü, etc.)...

I believe those are two separate issues. The first one is related to the use of different code pages with automatic conversion failing and I hope that can be addressed in the query used to return view's DDL code. The second is design issue, display of Unicode data, a very significant internal issue. We plan to address Unicode display issue in version 8.

I am glad that this task on the stack! :) And when we can hope for a major upgrade?

Version 8 is expected in the second half of 2016. We are indeed already working on v8.0 code branch. But no specific release date is known at this time.

Are any private builds going to be available for early testing of v8? Or a beta test campaign perhaps?

	Quote:
	any private builds going to be available for early testing of v8

Certainly, but they are not available yet. Unicode handling is the #1 priority for v8. It requires touching many parts of the existing code base, most importantly the internal data structures, and it's going to take a while to implement. As soon as we get something more or less ready to try, we will let you know.