Pavel Stehule writes:
> 2009/3/11 Simon Riggs :
>> I remember I had some differences between the way loading occurs at
>> session start and as a result of a LOAD command. I think there's
>> probably already a way of doing this - probably by checking for
>> something that would only be there *after
On Wed, 2009-03-11 at 14:45 +, Greg Stark wrote:
> On Wed, Mar 11, 2009 at 2:18 PM, Simon Riggs wrote:
> >
> >> It would be a huge
> >> maintenance headache since every time we change a structure that the
> >> parser works someone would have to maintain all those compatibility
> >> parsers.
>
On Wed, Mar 11, 2009 at 2:18 PM, Simon Riggs wrote:
>
>> It would be a huge
>> maintenance headache since every time we change a structure that the
>> parser works someone would have to maintain all those compatibility
>> parsers.
>
> If it's a plugin that "someone" isn't any concern of ours. Exte
2009/3/11 Simon Riggs :
>
> On Wed, 2009-03-11 at 11:09 +0100, Pavel Stehule wrote:
>
>> I am searching way to extensible parser (actually not bison, only
>> transformations). I propose parserHook (transformation part). One
>> Tom's objection is difference between heooked and unhooked parser. It
>>
On Wed, 2009-03-11 at 13:14 +, Greg Stark wrote:
> On Wed, Mar 11, 2009 at 12:56 PM, Simon Riggs wrote:
> >
> > In the longer term it will be very useful to have the ability to support
> > multiple language variants, including older PostgreSQL syntax to allow
> > legacy systems to work with P
On Wed, Mar 11, 2009 at 12:56 PM, Simon Riggs wrote:
>
> In the longer term it will be very useful to have the ability to support
> multiple language variants, including older PostgreSQL syntax to allow
> legacy systems to work with Postgres at the same time as allowing new
> development to contin
On Wed, 2009-03-11 at 11:09 +0100, Pavel Stehule wrote:
> I am searching way to extensible parser (actually not bison, only
> transformations). I propose parserHook (transformation part). One
> Tom's objection is difference between heooked and unhooked parser. It
> serious problem.
Do you mean h
Hello
I am searching way to extensible parser (actually not bison, only
transformations). I propose parserHook (transformation part). One
Tom's objection is difference between heooked and unhooked parser. It
serious problem.
I have one idea - only preloadable libraries. These libs have to be
spec
