You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Redshift version PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.71629
Client Operating System: Windows Server 2019
Problem description
When upgrading from driver version 1.5.9 -> 2.1.3, I saw that unicode strings were not coming through correctly. The old driver installer had a configuration item to enable or disable unicode support:
But this new driver has no such option.
I have the following test which I ran before and after the upgrade:
SELECT * FROM OPENQUERY([REDSHIFT], 'SELECT ''ぬるを'' AS UnicodeTest_openquery')
EXEC('SELECT ''ぬるを'' AS UnicodeTest_exec') AT [REDSHIFT]
On version 1.5.9, this returns the expected result:
Hi @alainbryden
Thank you for taking the time to report this issue. I appreciate your effort and will make sure it reaches the appropriate team for investigation as soon as possible.
@alainbryden
After discussing with my team, it turns out we have to extend our driver to support this feature. I will keep this ticket open for further updates.
Thanks
Version
2.1.3.0
PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.71629
Windows Server 2019
Problem description
When upgrading from driver version 1.5.9 -> 2.1.3, I saw that unicode strings were not coming through correctly. The old driver installer had a configuration item to enable or disable unicode support:
But this new driver has no such option.
I have the following test which I ran before and after the upgrade:
On version 1.5.9, this returns the expected result:
On 2.1.3, the column names survive, but the values are mangled:
We were upgrading to hopefully take advantage of ZSTD compression, but we use global datasets, so this regression is holding us back.
The text was updated successfully, but these errors were encountered: