| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | "Richards, Nina" <Nina(dot)Richards(at)oeaw(dot)ac(dot)at> |
| Cc: | "Watzinger, Alexander" <Alexander(dot)Watzinger(at)oeaw(dot)ac(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Support for dates before 4713 BC |
| Date: | 2024-10-17 00:17:01 |
| Message-ID: | CAApHDvomL7e49Y0ZyCu4ZrSq-mF7bcnq6cz+8_BwvNM4bL+Ruw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 17 Oct 2024 at 01:26, Richards, Nina <Nina(dot)Richards(at)oeaw(dot)ac(dot)at> wrote:
> Even though we know there was no calendar at that time, it would make our work much easier if we could use data before 4713 BC in the same way. Especially for statistical analyses and scientific dating methods (14C, dendrochronology), this would be a great benefit for us as well as the users of OpenAtlas.
>
>
> Are there, by any chance, news about this issue? Or are you aware of any suitable workarounds on the database level in the meantime?
It's by no means a trivial thing to do, but it is possible to
implement new types in PostgreSQL [1]. If you invented your own type,
you could significantly widen the upper and lower bounds when compared
with the standard date type.
David
[1] https://www.postgresql.org/docs/current/sql-createtype.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-10-17 00:36:12 | Re: Support for dates before 4713 BC |
| Previous Message | Andy Hartman | 2024-10-16 22:59:32 | Re: Backup |