Re: [HACKERS] psql NUL record and field separator

2012-02-08 Thread Abhijit Menon-Sen
At 2012-02-07 13:20:43 +0200, pete...@gmx.net wrote: Should we rename the options and/or add that to the documentation, or is the new behavior obvious and any new terminology would be too confusing? I agree there is potential for confusion either way. I tried to come up with a complete and

Re: [HACKERS] psql NUL record and field separator

2012-02-07 Thread Peter Eisentraut
On tor, 2012-01-26 at 19:00 +0530, Abhijit Menon-Sen wrote: At issue are (at least) these three lines from print_unaligned_text in src/bin/psql/print.c: 358 /* the last record needs to be concluded with a newline */ 359 if (need_recordsep) 360 fputc('\n',

Re: [HACKERS] psql NUL record and field separator

2012-01-26 Thread Abhijit Menon-Sen
At 2012-01-14 14:23:49 +0200, pete...@gmx.net wrote: Inspired by this question http://stackoverflow.com/questions/6857265 I have implemented a way to set the psql record and field separators to a zero byte (ASCII NUL character). Since this patch is in the commitfest, I had a look at it. I

[HACKERS] psql NUL record and field separator

2012-01-14 Thread Peter Eisentraut
Inspired by this question http://stackoverflow.com/questions/6857265 I have implemented a way to set the psql record and field separators to a zero byte (ASCII NUL character). This can be very useful in shell scripts to have an unambiguous separator. Other GNU tools such as find, grep, sort,