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

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Дата
Msg-id e4905524ce9d8cc006e0829d91f89001
обсуждение исходный текст
Ответ на Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')  (Mattias Kregert <matti@algonet.se>)
Список pgsql-hackers
>
> Mattias Kregert wrote:
> >
> > Bruce Momjian wrote:
> > >
> >
> > > I just think the WARN word coming up on users terminals is odd.  I can
> > > make the change in all the source files easily if we decide what the new
> > > error word should be.  Error?  Failure?
> > >
> >
> > Yes, that's one of the things I don't understand with PostgreSQL.
> > ERROR would be much better.
>
> How about ABORT ?

Sounds maybe a little too serious.  We currently use WARN a lot to
indicate errors in the supplied SQL statement.  Perhaps we need to make
the parser elog's ERROR, and the non-parser WARN's ABORT?  Is that good?
When can I make the change?  I don't want to mess up people's current work.

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

------------------------------

В списке pgsql-hackers по дате отправления: