View Single Post

   
  #6 (permalink)  
Old 04-17-2008, 11:23 PM
Tom Lane
 
Posts: n/a
Default Re: Adding \x escape processing to COPY, psql, backend

Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Here is a new version of the three \x hex support patches. I have added
> \x for psql variables, which is the last patch.


> I have IM'ed with Peter and he is now OK with the idea of supporting \x,
> with the underestanding that it doesn't take us any farther away from
> compatibility than we are now.


Peter may be OK with it, but I object strongly to adding this to SQL
literals. This is exactly *not* the direction we want to be going in.

I don't really see the point for COPY and psql, either.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Reply With Quote