From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Proposed patch for error locations |
Date: | 2006-03-13 14:22:35 |
Message-ID: | Pine.LNX.4.64.0603131505520.21383@briare.cri.ensmp.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces pgsql-patches |
Dear Tom,
> I haven't gone further than making it finger the locations of bogus column
> references, operators, and functions --- it's probably worth improving
> TypeCast and maybe a few other raw-parse-tree constructs too.
Yes. Other area would also benefit, such as type names:
psql: CREATE FUNCTION foo() RETURNS INTEGET LANGUAGE plpgsql AS ...
ERROR: type "integet" does not exist
That is a kind of "entry level" user features which are good for my
students ... as well as myself. Thus I'm looking forward to have more help
along those lines, although I cannot give a hand at the time.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-13 15:11:31 | Re: [PATCHES] Proposed patch for error locations |
Previous Message | Martijn van Oosterhout | 2006-03-13 11:43:31 | Re: Proposed patch for error locations |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-13 15:11:31 | Re: [PATCHES] Proposed patch for error locations |
Previous Message | Bruce Momjian | 2006-03-13 14:06:40 | Re: fix of some issues with multi-line query editing |