Re: [PATCHES] Better handling of parse errors

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Better handling of parse errors
Date: 2002-08-18 21:35:30
Message-ID: Pine.LNX.4.44.0208182329120.13718-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane writes:

> "Character 1" is correct as of the context that the parser is working
> in, namely the function body. I don't think we can do much to change
> that, but perhaps we could make the message read like
> ERROR: parser: parse error at or near "not" at character 1 of function body

That would be better.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2002-08-18 21:36:01 Re: Open 7.3 items
Previous Message Peter Eisentraut 2002-08-18 21:35:20 Re: [HACKERS] Documentation DTD

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2002-08-18 21:48:26 Re: BYTEA, indexes and "like"
Previous Message Joe Conway 2002-08-18 21:28:52 bytea operator bugs (was Re: [GENERAL] BYTEA, indexes and "like")