| From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Better handling of parse errors |
| Date: | 2002-08-06 12:18:00 |
| Message-ID: | Pine.LNX.4.21.0208062211200.16671-101000@linuxworld.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Hi all,
Attached is a small patch to scan.l for consideration. It hands
yyerror() the position in the query string of the token which caused a
parse error. It is not even close to an implementation of error handling
a-la SQL99 but it certainly makes debugging complicated queries easier.
I've done some testing and it appears to hit the offending token pretty
accurately.
Can anyone find a way to break this? If not, I'd love to see it in 7.3.
Gavin
| Attachment | Content-Type | Size |
|---|---|---|
| scanner.diff.gz | application/x-gzip | 872 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-08-06 12:20:25 | Re: DB-local usernames |
| Previous Message | Nigel J. Andrews | 2002-08-06 09:47:21 | Re: FUNC_MAX_ARGS benchmarks |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-08-06 12:23:54 | Re: Better handling of parse errors |
| Previous Message | Karel Zak | 2002-08-06 08:49:59 | Re: SQL99 CONVERT() function |