Normally I am pretty good about not disclosing work sensitive details. But we have a DB with employee data. Things were breaking earlier.
latest #6
We tracked the issue down to an insert statement which was attempting to set a date field for an employee record with a date of 02/04/2101.
sounds like ... no, it doesn't. It does remind me of some of the Perl date display silliness of 2000 or so.
Folks had a habit of concatenating and displaying "19100" for the year because they didn't read the docs.
Someone entered it wrong via the 10-key. Oops!
back to top