| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | protodef(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: optionally schema-qualified for table_name |
| Date: | 2020-03-22 20:15:18 |
| Message-ID: | 20200322201518.GB2031@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Sun, Mar 22, 2020 at 03:05:01PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I see what you mean. The attached patch fixes this, as well as
> > adjusting the error message. I didn't see any other cases.
>
> 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.
I don't see any other messages with "table.column". Do you want?
Specify OWNED BY column or OWNED BY NONE.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-03-22 22:20:04 | Re: optionally schema-qualified for table_name |
| Previous Message | Tom Lane | 2020-03-22 19:05:01 | Re: optionally schema-qualified for table_name |