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

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev)
Cc: matti(at)algonet(dot)se, hackers(at)postgreSQL(dot)org
Subject: Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Date: 1998-01-05 04:43:21
Message-ID: 199801050443.XAA27259@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)us

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vadim B. Mikheev 1998-01-05 04:51:30 Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Previous Message Bruce Momjian 1998-01-05 04:35:04 ERROR/ABORT message