Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Bug: PostgreSQL column of type date is misinterpreted for dates < 0100-01-01 #8753

Open
1 task done
salim-b opened this issue Jun 14, 2024 · 0 comments
Open
1 task done

Comments

@salim-b
Copy link
Contributor

salim-b commented Jun 14, 2024

Please confirm if bug report does NOT exist already ?

  • I confirm there is no existing issue for this

Steps to reproduce ?

PostgreSQL's date column type supports dates from 4713 BC to 5874897 AD. But dates before 0100-01-01 in an external PostgreSQL DB are wrongly displayed in NocoDB (as 1901-01-01) and values before 0100-01-01 are wrongly written from NocoDB (e.g. 0099-01-01 wrongly becomes 1999-01-01).

Desired Behavior

NocoDB should properly support date fields in external PostgreSQL DB's.

Project Details

Node: v20.12.1
Arch: x64
Platform: linux
Docker: false
RootDB: sqlite3
PackageVersion: 0.250.1

Attachments

No response

@salim-b salim-b changed the title 🐛 Bug: PostgreSQL column of type date is misinterpreted for dates < 0100-01-01 🐛 Bug: PostgreSQL column of type date is misinterpreted for dates < 0100-01-01 Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🏌️ Open
Development

No branches or pull requests

1 participant