From: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, <pgsql-patches(at)postgresql(dot)org>, <david(at)fetter(dot)org>, <kzak(at)redhat(dot)com>, <hsn(at)netmag(dot)cz> |
Subject: | Re: Oracle date type compat. functions: next_day, last_day, |
Date: | 2005-06-02 16:53:21 |
Message-ID: | Pine.LNX.4.44.0506021836330.4622-100000@kix.fsv.cvut.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
>
> Why not a pgFoundry project called Oracle-Compat or something? There
> are plenty of functions etc... that can be included in the package as a
> whole.
>
> Once it is large enough, push it to contrib or vie for core support.
>
Is exists. Not in very usefull state, true.
http://pgfoundry.org/projects/orafce/
I have two motivations for commit in main code. I don't speak about
functions like add_months (it's can be in sontrib, for me). a) next_day,
last_day are usefull, I am sure, and I wont to use them. b) some functions
need patch to parser - greatest, least and decode. I don't know way to
implemented its efective like normal contrib functions. And if they are
outside main tree, you have to maintain patch :-(.
I expect so less used functions will go to contrib: LNNVL, .. but some
functions can by general usefull. There is WIDTH_BUCKET in core too now.
Who use it?
Pavel Stehule
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-02 17:49:07 | Re: Oracle date type compat. functions: next_day, last_day, |
Previous Message | David Fetter | 2005-06-02 16:37:38 | Re: Oracle date type compat. functions: next_day, last_day, |