Skip site navigation (1) Skip section navigation (2)

Re: Proposed patch for error locations

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 (view raw or flat)
Thread:
Lists: pgsql-interfacespgsql-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.

In response to

pgsql-patches by date

Next:From: Tom LaneDate: 2006-03-13 15:11:31
Subject: Re: [PATCHES] Proposed patch for error locations
Previous:From: Bruce MomjianDate: 2006-03-13 14:06:40
Subject: Re: fix of some issues with multi-line query editing

pgsql-interfaces by date

Next:From: Tom LaneDate: 2006-03-13 15:11:31
Subject: Re: [PATCHES] Proposed patch for error locations
Previous:From: Martijn van OosterhoutDate: 2006-03-13 11:43:31
Subject: Re: Proposed patch for error locations

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group