@TotalDataLoss not sue how familiar you are with other programming languages and systems and their handling of date and time variables. From my experience I can say: they are all different and nearly all have some quirks and special characteristics especially when it comes to time zones and end of year settings, also weeks of year and so on (UNIX Timestamps, Excel, SPSS, ORACLE, Cloudera BigData, R, Python …). So if you have to deal with such variables I would always check twice if I have covered all the quirks and my system does what I want. Sometimes it also depends on extra settings within the database (or system).
Sometimes it can be best to store date and time variables just as strings or ‘readable numbers’ (20220528) and then convert them later in the system you want. And always check the fringe cases.