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

From Peter T Mount
Subject Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Date
Msg-id Pine.LNX.3.95.980104121118.18896A-100000@maidast
Whole thread Raw
In response to Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')  (Mattias Kregert <matti@algonet.se>)
List pgsql-hackers
On Sat, 3 Jan 1998, Bruce Momjian wrote:

> 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.

This shouldn't affect JDBC. The only thing that would break things, is if
the notification sent by the "show datestyle" statement is changed.

--
Peter T Mount  petermount@earthling.net or pmount@maidast.demon.co.uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk



pgsql-hackers by date:

Previous
From: Peter T Mount
Date:
Subject: Re: [HACKERS] Re: [QUESTIONS] tuple is too big?
Next
From: Integration
Date:
Subject: config.h/Followup FOLLOWUP