| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, yangyz <1197620467(at)qq(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Addition and subtraction operations for the interval and integer types |
| Date: | 2026-02-26 09:44:31 |
| Message-ID: | 6f9eb50c34cbfe7f214100b056d5d6147aa3c845.camel@oopsware.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Am Mittwoch, dem 25.02.2026 um 23:30 -0700 schrieb David G. Johnston:
> On Wednesday, February 25, 2026, yangyz <1197620467(at)qq(dot)com> wrote:
> >
> > In order to enhance the compatibility
> > between Oracle and PostgreSQL, I implemented it.
> >
>
> This isn’t all that appealing to me. There isn’t really a goal of
> increased compatibility’s aside from with the SQL Standard
> (extensions can
> accept that burden IMO). And the utility of preventing people from
> having
> to explicitly write the word ‘day’ is marginal. And given the
> already
> numerous ways to combine data types in date/time I hesitate to add
> yet more.
And there's the orafce extension[1] which adds extensive oracle
datetime compatibility to Postgres (including a more or less compatible
oracle.date type). This is far more useful since it also adds many of
the Oracle functions for datetime operations, too (like sysdate, ...).
[1] https://github.com/orafce/orafce
--
Thanks,
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shin Berg | 2026-02-26 09:52:38 | Re: Inconsistency in owner assignment between INDEX and STATISTICS |
| Previous Message | Andrei Lepikhov | 2026-02-26 09:38:33 | Re: Skipping schema changes in publication |