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
Describe the bug
"Export Data Query" is not accepting queries with multiple lines.
Error message retrieved from Processes tab says;
\copy: parse error at end of line
To Reproduce
Steps to reproduce the behavior:
Right click to database
Click on "Export Data Using Query..."
Navigate to "Query" tab
Enter an example query with multiple lines to "Export Data Query" textbox (sample given below)
Click OK
???
Profit
Example query;
select name
from tablebaz
limit31
Expected behavior
¿Export the data?
Error message
\copy: parse error at end of line
Desktop (please complete the following information):
OS: Windows 11
Version: 24H2, 26100.4061
Mode: Desktop
Additional context
Exact same query works if I remove all the new line characters and shrink it down to a single line query.
I've take a look at the source code and I think the new lines aren't handled.
Perhaps the problem can be solved by removing new line characters in the "query" by adding onSave property to the dialogProps and sanitizing the new lines;
Describe the bug
"Export Data Query" is not accepting queries with multiple lines.
Error message retrieved from Processes tab says;
To Reproduce
Steps to reproduce the behavior:
Example query;
Expected behavior
¿Export the data?
Error message
\copy: parse error at end of line
Desktop (please complete the following information):
Additional context
Exact same query works if I remove all the new line characters and shrink it down to a single line query.
I've take a look at the source code and I think the new lines aren't handled.
Perhaps the problem can be solved by removing new line characters in the "query" by adding
onSave
property to thedialogProps
and sanitizing the new lines;pgadmin4/web/pgadmin/tools/import_export/static/js/import_export.js
Line 184 in 3286b4e
The text was updated successfully, but these errors were encountered: