From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-hackers(at)postgresql(dot)org, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] \copy (query) delimiter syntax error |
Date: | 2007-02-04 21:18:19 |
Message-ID: | 3964.1170623899@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> The consequence will be, though, that psql will accept a syntax for
> "\copy (query) ..." that the corresponding backend command would reject
> were we not transforming it. That strikes me as potentially confusing.
Perhaps. What about plan B: remove the legacy syntax support in \copy?
IIRC it has not been documented since 7.2, so maybe we can finally throw
it overboard. Thoughts?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-02-04 21:20:25 | Re: [HACKERS] \copy (query) delimiter syntax error |
Previous Message | Jeremy Drake | 2007-02-04 21:00:12 | Re: [HACKERS] writing new regexp functions |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-02-04 21:20:25 | Re: [HACKERS] \copy (query) delimiter syntax error |
Previous Message | Jeremy Drake | 2007-02-04 21:00:12 | Re: [HACKERS] writing new regexp functions |