fne8w2ah@lemmy.world to World News@lemmy.worldEnglish · 9 months agoLeap year software glitch closes fuel pumps across New Zealandwww.straitstimes.comexternal-linkmessage-square5fedilinkarrow-up196arrow-down13cross-posted to: [email protected]
arrow-up193arrow-down1external-linkLeap year software glitch closes fuel pumps across New Zealandwww.straitstimes.comfne8w2ah@lemmy.world to World News@lemmy.worldEnglish · 9 months agomessage-square5fedilinkcross-posted to: [email protected]
minus-squarenarc0tic_bird@lemm.eelinkfedilinkEnglisharrow-up40·9 months agoSomeone wrote their own date library.
minus-squarestoly@lemmy.worldlinkfedilinkEnglisharrow-up4·9 months agoI was thinking to myself that this system MUST be less than 4 years old or it would have happened last February 29.
minus-squareelmicha@feddit.delinkfedilinkEnglisharrow-up2·9 months agoI hit a similar bug today where I had used SYSDATE - NUMTOYMINTERVAL(2, 'year') in Oracle. I don’t remember why I didn’t use sysdate - 2*365 instead, which works without problems for my use case (I don’t care about one day more or less). But I would have appreciated if the compiler or the IDE would have yelled at me.
Someone wrote their own date library.
Never write your own date library
I was thinking to myself that this system MUST be less than 4 years old or it would have happened last February 29.
classic!
I hit a similar bug today where I had used
in Oracle. I don’t remember why I didn’t use
sysdate - 2*365instead, which works without problems for my use case (I don’t care about one day more or less). But I would have appreciated if the compiler or the IDE would have yelled at me.