public inbox for [email protected]  
help / color / mirror / Atom feed
From: Tom Lane <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Clément Prévost <[email protected]>
Cc: [email protected]
Subject: Re: Documentation on information_ schema columns that does not exist
Date: Wed, 03 Aug 2016 15:27:27 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CABaKae8+p6=zhCM=Qrq_GMN88pFqjb5EgHpy9bjGaKZfvJmzZA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CABaKae8UVSGwyQ-QFKxsk9obqyBpYOsCfgO_jNP_Y8iTJOuJxw@mail.gmail.com>
	<CABaKae8G=XNgsQW6eFzkjbQ4d=05L0siddRp1R6dMVZJtYwixA@mail.gmail.com>
	<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

Peter Eisentraut <[email protected]> writes:
> On 5/31/15 8:27 PM, Clément Prévost 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


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs



view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Documentation on information_ schema columns that does not exist
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox