| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Clément Prévost <prevostclement(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Documentation on information_ schema columns that does not exist |
| Date: | 2016-08-03 19:27:27 |
| Message-ID: | 15356.1470252447@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 5/31/15 8:27 PM, Clment Prvost wrote:
>> Here is another patch to fix the name of the column
>> information_schema.routines.result_cast_char_set_name that was
>> mistakenly named result_cast_character_set_name.
> This one is actually named result_cast_character_set_name in the
> standard, although that might be a mistake. Anyway, our documentation
> doesn't match our implementation, so one of them has to change.
Hm, yeah, I think I vote with the "it's a mistake" camp. The adjacent
columns are named "result_cast_char_set_whatever", and there are
occurrences of result_cast_char_set_name elsewhere, for example
in the method_specifications view.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | denisa.cirstescu | 2016-08-05 10:48:37 | Undocumented behavior od DROP SCHEMA ... CASCADE |
| Previous Message | Peter Eisentraut | 2016-08-03 19:13:53 | Re: Might be worth mentioning that temp_tablespaces can contain duplicate values |