We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In PostgreSQL, if an HSTORE column contains a newline, Jailer will export the value as...
'"key"=>"value' || chr(10) || 'with newlines"' :: hstore
... which results in the following error when executing in psql:
psql
psql=# select '"key"=>"value' || chr(10) || 'with newlines"' :: hstore; ERROR: Syntax error near "n" at position 5 LINE 1: select '"key"=>"value' || chr(10) || 'with newlines"' :: hst...
However, if the HSTORE value were to be exported with parantheses, as shown below...
('"key"=>"value' || chr(10) || 'with newlines"') :: hstore
...I believe it would work:
psql=# select ('"key"=>"value' || chr(10) || 'with newlines"') :: hstore; hstore ---------------- "key"=>"value + with newlines" (1 row)
The text was updated successfully, but these errors were encountered:
Thank you for the error report! This has been fixed in release 16.4.
Sorry, something went wrong.
@Wisser thank you for the quick response. Actually, I discovered this to be a bug for TEXT columns as well. Does 16.4 fix that as well?
TEXT
Yes, it works for all literals. Let me know if you find any other issues.
Wisser
No branches or pull requests
In PostgreSQL, if an HSTORE column contains a newline, Jailer will export the value as...
... which results in the following error when executing in
psql
:However, if the HSTORE value were to be exported with parantheses, as shown below...
...I believe it would work:
The text was updated successfully, but these errors were encountered: