| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: hooking parser |
| Date: | 2009-02-18 15:30:12 |
| Message-ID: | 6905.1234971012@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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.
AFAIK, the Oracle behavior is just about entirely unrelated to the
parser --- it's a matter of runtime comparison behavior. It is
certainly *not* restricted to literal NULL/'' constants, which is the
only case that a parser hack can deal with.
There's some interesting comments here:
http://stackoverflow.com/questions/203493/why-does-oracle-9i-treat-an-empty-string-as-null
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-02-18 15:32:03 | Re: SE-PostgreSQL and row level security |
| Previous Message | Andrew Chernow | 2009-02-18 15:28:36 | Re: PQinitSSL broken in some use casesf |