Re: Replacing plpgsql's lexer - Mailing list pgsql-hackers

From Grzegorz Jaskiewicz
Subject Re: Replacing plpgsql's lexer
Date
Msg-id 1FD7BF1E-AFD4-4374-A0C1-4AA1D6A9349F@pointblue.com.pl
Whole thread Raw
In response to Re: Replacing plpgsql's lexer  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Replacing plpgsql's lexer  (Greg Stark <stark@enterprisedb.com>)
List pgsql-hackers
On 19 Apr 2009, at 17:42, Tom Lane wrote:
>
> The attached proposed patch rips out plpgsql's handling of comments  
> and
> string literals, and puts in scanner rules that are extracted from the
> core lexer (but simplified in a few places where we don't need all the
> complexity).  The net user-visible effects should be:
>
>
> Comments?

Will it also mean, that queries are going to be analyzed deeper ?
Ie, afaik I am able now to create plpgsql function, that tries to run  
query accessing non existent table, or columns.
Or, if I rename column/table/relation now, views, etc are getting  
updated - but not plpgsql functions. Will that change with your patch ?



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Replacing plpgsql's lexer
Next
From: Greg Stark
Date:
Subject: Re: Replacing plpgsql's lexer