Re: optionally schema-qualified for table_name

On Sun, Mar 22, 2020 at 06:20:04PM -0400, Tom Lane wrote: > Bruce Momjian 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

Re: optionally schema-qualified for table_name

Bruce Momjian 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: >

Re: optionally schema-qualified for table_name

On Sun, Mar 22, 2020 at 03:05:01PM -0400, Tom Lane wrote: > Bruce Momjian 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

Re: optionally schema-qualified for table_name

Bruce Momjian 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