-
Notifications
You must be signed in to change notification settings - Fork 39
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
Postgres DatetimeFieldOverflow #16
Comments
mrkamel
pushed a commit
that referenced
this issue
Feb 24, 2015
Hi, thanks for the report. Should now be fixed in master by limiting the year-recognition to YYYY. However, now we're running into a Y10K bug :-) |
Awesome, thanks for the quick fix! |
I'll set a calendar reminder for 9999 to file a bug : ) |
v1.0.6 is out to officially fix this |
Great, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have had a few production errors like this one:
The user is searching for
00393488235373
. Searchcop searches a number of fields, including some which are date/timestamps, treating this integer as a year. Postgres gets upset because the year is too large for it, and crashes, something like:The text was updated successfully, but these errors were encountered: