-
Notifications
You must be signed in to change notification settings - Fork 86
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
COPY no longer blows up, but... #111
Comments
Sadly, interested != available.
… On Oct 17, 2018, at 12:24 PM, Lukas Fittl ***@***.***> wrote:
@benchub <https://github.com/benchub> Yup, thats not good :)
Either you or @herwinw <https://github.com/herwinw> interested in making a patch?
I believe all thats needed is to call deparse on the query variable and insert that when needed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#111 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABzq-kp4COVt-T7icIl63z3V_sBcVSSiks5ul4PTgaJpZM4XiVFD>.
|
Maybe next week |
I guess this is not the only location where some functionality in deparse is missing, so more cases like this are likely to appear. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
print PgQuery.parse("COPY (SELECT 1 from foo) TO STDOUT").deparse
returns just
COPY TO STDOUT
That seems suboptimal.
The text was updated successfully, but these errors were encountered: