Invalid extreme date time value accepted in PostgreSQL causes "Double time specification" error
Open
@luka-nextcloud is already working on this.
Since Sep 11, 2026.
1. to develop
bug
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
In PostgreSQL, an extreme timestamp value (for example, 99999-09-11 02:00:00) is accepted as valid and stored. This causes errors "Double time specification" when parse record (especially when run background job CardDescriptionActivity). So, the date time values should be validated before being saved into db.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.