qaz@lemmy.world to Memes@lemmy.ml · 1 year agoStandards shouldn't be behind a paywalllemmy.worldimagemessage-square100fedilinkarrow-up1663arrow-down134file-textcross-posted to: iso8601@lemmy.sdf.org
arrow-up1629arrow-down1imageStandards shouldn't be behind a paywalllemmy.worldqaz@lemmy.world to Memes@lemmy.ml · 1 year agomessage-square100fedilinkfile-textcross-posted to: iso8601@lemmy.sdf.org
ISO 8601 is paywalled RFC allows a space instead of a T (e.g. 2020-12-09 16:09:…) which is nicer to read.
minus-squarelowleveldata@programming.devlinkfedilinkarrow-up133arrow-down25·1 year agoA space is more problematic than a T tho
minus-squarelowleveldata@programming.devlinkfedilinkarrow-up67arrow-down24·1 year agoFor a skilled pro like you I suggest using epoch time for everything
minus-squaredatelmd5sum@lemmy.worldlinkfedilinkarrow-up4·1 year agoCassandra uses epoch milliseconds for timestamping snapshots. This means that each node will have a different name for the same snapshot. Trivially solved with truncating the timestamp with * wildcard, but just… why?
minus-squareTransporter Room 3@startrek.websitelinkfedilinkarrow-up33arrow-down3·1 year agoAny other day I’d see this get laughs, but I guess people are bitchier this time of day. I’d write down the ISO timecode I’m talking about, but I can’t afford it.
A space is more problematic than a T tho
Skill issue
For a skilled pro like you I suggest using epoch time for everything
Cassandra uses epoch milliseconds for timestamping snapshots. This means that each node will have a different name for the same snapshot. Trivially solved with truncating the timestamp with * wildcard, but just… why?
Any other day I’d see this get laughs, but I guess people are bitchier this time of day.
I’d write down the ISO timecode I’m talking about, but I can’t afford it.