From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: protodef@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: optionally schema-qualified for table_name
Date: Sun, 22 Mar 2020 18:20:04 -0400
Message-ID: <4628.1584915604@sss.pgh.pa.us> (raw)
In-Reply-To: <20200322201518.GB2031@momjian.us>
References: <158399268229.5708.13296960177949398026@wrigleys.postgresql.org>
<20200322001310.GA2031@momjian.us>
<22707.1584903901@sss.pgh.pa.us>
<20200322201518.GB2031@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> On Sun, Mar 22, 2020 at 03:05:01PM -0400, Tom Lane wrote:
>> I don't really think this is an improvement, mainly because that
>> error message is inventing a notation that we do not use in any
>> other error message.
> What do you suggest? The current message is:
> Specify OWNED BY table.column or OWNED BY NONE.
Yeah, and I think that's okay as-is, or at least we can't make it better
without fairly whole-sale changes of our documentation practices.
The fact that a table name can be schema-qualified is usually implicit,
and I don't see why this place cries out for making it explicit
more than other places. You could as well complain that there's
nothing explicit here about double-quoting practices.
regards, tom lane
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: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, protodef@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: optionally schema-qualified for table_name
In-Reply-To: <4628.1584915604@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox