Re: Better handling of parse errors
От | Gavin Sherry |
---|---|
Тема | Re: Better handling of parse errors |
Дата | |
Msg-id | Pine.LNX.4.21.0208150025360.24839-101000@linuxworld.com.au обсуждение исходный текст |
Ответ на | Re: Better handling of parse errors (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Better handling of parse errors
Re: Better handling of parse errors Re: [PATCHES] Better handling of parse errors |
Список | pgsql-hackers |
On Wed, 14 Aug 2002, Tom Lane wrote: > Gavin Sherry <swm@linuxworld.com.au> writes: > > ... do we want to modify every 7.2 error message? > > Nyet ... but I don't think tacking an offset onto the end of > "parse error at or near foo" messages is likely to cause the > sort of generalized havoc you suggest ... In that case, attached is a patch which locates the beginning of the offending token more efficiently (per your suggestion of using scanbuf). The new patch does the same as before: template1=# select * frum pg_class; ERROR: parser: parse error at or near "frum" at character 10 It also implement's Tom's suggestion: template1=# select * from pg_class where\g ERROR: parse: parse error at end of input Gavin
В списке pgsql-hackers по дате отправления: