Correct 0 date values in SQL views to NULL values
In circtrans and finespaid views (and maybe more views) there are several dates that are showing a value of 0 (which displays as 1969-12-31 due to UNIX date formatting).
Dates do not have a value of 0, they can however, have a value of NULL, which is already how things work with other dates in the system, like the bib record cataloguingdategmt.
This should be fixed for any dates in the system, not because anyone may or may not vote for it, but because it is both inaccurate and inconsistent.
I logged this as a ticket, but was told to put an entry here to fix it. While I think the idea exchange is a great idea for enhancements or changes, I strongly believe that bugs should be corrected and not rely on voting to be implemented.
AdminJulie Cole
(Admin, Innovative)
shared this idea
-
Phil Shirley
commented
This does seem like a bug fix and not an enhancement idea.
-
Jeremy Goldstein
commented
These errors will occasionally show up in the client too so this is a bit broader of an issue than just the sql views.
There’s a glitch with the self checkout feature in our mobile app where if an item is rapidly scanned twice it doesn’t get checked out correctly and the only reason we know about that is the items wind up with a due date of 1969.
-
Lloyd Chittenden
commented
**** straight. We shouldn't vote on bugs. Bugs should just get fixed.