| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Handling of \ in array data display |
| Date: | 2006-08-18 23:07:06 |
| Message-ID: | 200608181607.07332.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro,
> tarr[1] does not have a \, because it was eaten by the parser (so \y is
> the same as a plain y). tarr[2] does have a single backslash, which for
> output purposes is shown escaped with another backslash when part of an
> array, but unescaped when not. I'm not sure if this qualifies as a bug
> or not.
I think it does. It's not consistent with how text values not in an array
are displayed. The whole reason I reported it was because of a user
thinking their data wasn't being saved correctly, so it's causing
confusion.
FWIW, I personaly think we should be using the ARRAY[] format for display
anyway, but that would break some backwards compatibility ...
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-19 00:08:42 | Re: Handling of \ in array data display |
| Previous Message | Alvaro Herrera | 2006-08-18 22:32:17 | Re: Handling of \ in array data display |