Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unicode column values are corrupted #24

Open
alainbryden opened this issue Aug 13, 2024 · 2 comments
Open

Unicode column values are corrupted #24

alainbryden opened this issue Aug 13, 2024 · 2 comments

Comments

@alainbryden
Copy link

Version

  • Driver version: 2.1.3.0
  • 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:
image

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:

るを_unicodetest_openquery
ぬるを
るを_unicodetest_exec
ぬるを

image

On 2.1.3, the column names survive, but the values are mangled:

るを_unicodetest_openquery
�るを
るを_unicodetest_exec
�るを

image

We were upgrading to hopefully take advantage of ZSTD compression, but we use global datasets, so this regression is holding us back.

@vahid110
Copy link
Contributor

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.

@vahid110
Copy link
Contributor

vahid110 commented Oct 8, 2024

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants