Bruce Momjian writes:
> The attached patch fixes the warning you received by adding E'' strings
> to the \copy arguments, and adds it for the other backslash commands
> like \d.
Further comment on this: I don't think we want all these places
individually making this sort of decision. What they s
Tom Lane wrote:
> Bruce Momjian writes:
> > The attached patch fixes the warning you received by adding E'' strings
> > to the \copy arguments, and adds it for the other backslash commands
> > like \d.
>
> You missed the point entirely Bruce. The problem is that \copy's
> argument parsing won't
Tom Lane wrote:
> Bruce Momjian writes:
> > The attached patch fixes the warning you received by adding E'' strings
> > to the \copy arguments, and adds it for the other backslash commands
> > like \d.
>
> Further comment on this: I don't think we want all these places
> individually making this
Bruce Momjian writes:
> Right. I think the question is whether we want all psql strings to
> accept backslashes, and hence not support E'' at all for psql commands.
> I figured that made the most sense.
I'm not convinced. Wouldn't it be better if psql commands track the
backend syntax? With st
Tom Lane wrote:
> Bruce Momjian writes:
> > Right. I think the question is whether we want all psql strings to
> > accept backslashes, and hence not support E'' at all for psql commands.
> > I figured that made the most sense.
>
> I'm not convinced. Wouldn't it be better if psql commands track
