From: | George Gensure <werkt0(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: patch - Report the schema along table name in a referential failure error message |
Date: | 2009-11-17 05:41:53 |
Message-ID: | b47db0340911162141r785a3c11va2a993979be680b0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Nov 15, 2009 at 1:43 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> George Gensure wrote:
>>
>> This begs a bigger question: what's *really* easy or low barrier to
>> entry for very light contributors like myself? - I've got time, I like
>> the product, I need to know what's going to get you a win, I may not
>> be gunning particularly for the feature myself.
>
>
> The TODO list at <http://wiki.postgresql.org/wiki/Todo> doesn't seem to have
> a huge number or [E] items. Maybe we need a bit of a brainstorm to come up
> with a few more.
>
> The one I just started talking about (using param names in SQL functions)
> might not be terribly hard, depending on your coding skills, since it would
> be making use of the new parser hooks feature that Tom has just done the
> heavy lifting on.
>
> cheers
>
> andrew
>
There's some tricky stuff in here to say the least. Doesn't look like
param names are kept anywhere past the parser - gonna have to have it
follow through a bunch of functions to reach
parse_(fixed|variable)_parameters. The p_post_columnref_hook you
alluded to will help once I have the names though, so thanks :)
-George
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Hunsaker | 2009-11-17 06:15:05 | Re: Writeable CTE patch |
Previous Message | Itagaki Takahiro | 2009-11-17 05:19:58 | Re: UTF8 with BOM support in psql |