Pg suffers from Y10K problem

[moll]

This is because of dateMatcher in textParsers.js expects years to be 4 characters. https://en.wikipedia.org/wiki/Y10K

[booo]

Thanks for reporting the problem. Can you provide us with a few lines of code to reproduce the problem or a failing test case?

[moll]

Well, just create a date column in the database and insert a date above 10K there. ;)

[booo]

Something like:

SELECT DATE '20000-01-01'

[domino14]

Can this be handled in another few thousand years?

[moll]

Sadly, no. Unless all PostgreSQL users so far have been religious, the world also started more than 10k years ago. ;)

[benighted]

Unfortunately PostgreSQL does not support dates early than 4713 BCE (see manual). However I did fix pg's y10k issue with pull request #480 so you can record your pet dinosaur's birth date whenever PostgreSQL adds support for that date. 😄

[moll]

Cool. Thanks, @benighted! Life is difficult for us time-travelers.

[charmander]

This is fixed now, right?

[brianc]

This is fixed now, correct. Thanks @charmander - I was stuck under the rock of working too many hours at my startup not having enough time to work on this.