MIME-Version: 1.0
References: <0af9ebc00dca444cbd3c5e07752bc5f9@oeaw.ac.at>
In-Reply-To: <0af9ebc00dca444cbd3c5e07752bc5f9@oeaw.ac.at>
From: David Rowley <dgrowleyml@gmail.com>
Date: Thu, 17 Oct 2024 13:17:01 +1300
Message-ID: <CAApHDvomL7e49Y0ZyCu4ZrSq-mF7bcnq6cz+8_BwvNM4bL+Ruw@mail.gmail.com>
Subject: Re: Support for dates before 4713 BC
To: "Richards, Nina" <Nina.Richards@oeaw.ac.at>
Cc: "Watzinger, Alexander" <Alexander.Watzinger@oeaw.ac.at>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAApHDvomL7e49Y0ZyCu4ZrSq-mF7bcnq6cz%2B8_BwvNM4bL%2BRuw%40mail.gmail.com>
Precedence: bulk

On Thu, 17 Oct 2024 at 01:26, Richards, Nina <Nina.Richards@oeaw.ac.at> wro=
te:
> 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. Espe=
cially for statistical analyses and scientific dating methods (14C, dendroc=
hronology), this would be a great benefit for us as well as the users of Op=
enAtlas.
>
>
> 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