| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: control character check in JSON type seems broken |
| Date: | 2012-06-09 14:31:29 |
| Message-ID: | 27930.1339252289@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Jun 4, 2012 at 8:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> And so is that. IMO the error reporting in this module could stand to
>> be reviewed altogether for compliance with our message guidelines.
>> (For starters, why is it using errdetail_internal?) I refrained from
>> editorializing on-the-fly, but I'm not too pleased with what I saw.
> Huh. I have no idea why I thought errdetail_internal was a good idea.
> Should we just change all those to errdetail?
Yeah, they're clearly user-facing so I see no reason why they shouldn't
be translatable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2012-06-09 21:18:10 | Re: BUG #6680: error para ingresar |
| Previous Message | Dean Rasheed | 2012-06-09 09:40:25 | Tab completion of function arguments not working in all cases |