Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c') - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Date
Msg-id 199801050443.XAA27259@candle.pha.pa.us
Whole thread Raw
In response to Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')  ("Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>)
List pgsql-hackers
>
> Bruce Momjian wrote:
> >
> > > ABORT means that transaction is ABORTed.
> > > Will ERROR mean something else ?
> > > Why should we use two different flag-words for the same thing ?
> > > Note, that I don't object against using ERROR, but against using two words.
> >
> > I wanted two words to distinguish between user errors like a mis-spelled
> > field name, and internal errors like btree failure messages.
> >
> > Make sense?
>
> No, for me. Do Informix, Oracle, etc use two words ?
> What benefit of special "in-parser-error" word for user - in any case
> user will read error message itself to understand what caused error.

OK, if no one likes my idea in the next day, I will make them all ERROR.

--
Bruce Momjian
maillist@candle.pha.pa.us

pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] include/config.h FOLLOWUP
Next
From: darrenk@insightdist.com (Darren King)
Date:
Subject: Re: [HACKERS] include/config.h FOLLOWUP