Feature #1004
open
Dates before 4713 BC
Description
Dates before 4713 BC are problematic because they can't be saved as a PostgreSQL timestamp.
One solution would be to implement a parallel date system (e.g. using only years) but this would be way to cumbersome and error prone, we really like using the database for date operations.
So I ask in the PostgreSQL mailing list about it.
https://www.postgresql.org/message-id/ca438ff8331c4e109aa1b75a130948ac%40oeaw.ac.at
Updated by Alexander Watzinger over 1 year ago
- Description updated (diff)
One solution would be to implement a parallel date system (e.g. using only years) but this would be way to cumbersome and error prone, we really like using the database for date operations.
So I ask in the PostgreSQL mailing list about it: https://www.postgresql.org/message-id/ca438ff8331c4e109aa1b75a130948ac%40oeaw.ac.at
After it passed the moderation I got responses immediately. None of them saying they would implement it but still great it got taken seriously and got some feedback. Maybe Stefan or somebody else want to join this discussion?
Updated by Alexander Watzinger over 1 year ago
Great news, the people at the PostgreSQL mailing list (https://www.postgresql.org/message-id/ca438ff8331c4e109aa1b75a130948ac%40oeaw.ac.at) were very friendly and supporting. They are now discussing how this could be implemented and they will maybe do it in 2023. Anyway, it is very nice they take the time looking into it.
Updated by Nina Richards about 1 year ago
Is there any news about this issue? We have finds and sites to track within bITEM that are from 50.000 BC and it is not possible.
Updated by Alexander Watzinger about 1 year ago
- Status changed from Acknowledged to Assigned
- Assignee set to Stefan Eichert
I haven't heard anything new. Maybe Stefan, whom I just assigned it to, would like to post in the mailing list again.
Just to keep things going and to show our continued interest in this topic.