From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP: hooking parser |
Date: | 2009-02-19 07:58:19 |
Message-ID: | 162867790902182358x73b3abfdtb5582287ae0ad7fc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/2/18 Peter Eisentraut <peter_e(at)gmx(dot)net>:
> Pavel Stehule wrote:
>>
>> 2009/2/16 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>>>
>>> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>>>>
>>>> Next sample of parser hook using:
>>>> attachment contains module that transform every empty string to null.
>>>> I am not sure, if this behave is exactly compatible with Oracle,
>>>
>>> Surely a parser hook like this would have nothing whatsoever to do
>>> with Oracle's behavior.
>>>
>>> regards, tom lane
>>>
>>
>> it's maybe too much simple :). It is sample that have to show possibility.
>
> I'd be quite interested to support some kind of hook to deal with this
> Oracle null issue. It would be a great help for porting projects.
>
> However, doing this properly is probably more complex and needs further
> thought. I'd suggest writing a type of regression test first for Oracle
> null behavior and then evaluating any kind of hook or hack against that
+ 1
regards
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-02-19 08:31:22 | Re: Doubts about EvalPlanQual |
Previous Message | Heikki Linnakangas | 2009-02-19 07:35:14 | Re: Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |