Re: patch - Report the schema along table name in a referential failure error message - Mailing list pgsql-hackers

From George Gensure
Subject Re: patch - Report the schema along table name in a referential failure error message
Date
Msg-id b47db0340911162141r785a3c11va2a993979be680b0@mail.gmail.com
Whole thread Raw
In response to Re: patch - Report the schema along table name in a referential failure error message  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: patch - Report the schema along table name in a referential failure error message
List pgsql-hackers
On Sun, Nov 15, 2009 at 1:43 PM, Andrew Dunstan <andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Itagaki Takahiro
Date:
Subject: Re: UTF8 with BOM support in psql
Next
From: Alex Hunsaker
Date:
Subject: Re: Writeable CTE patch