![]() One option to handle the potential ambiguity of date/time is to define a common denominator of what date and time values mean in our database. However, if exact and accurate time information is important for the purpose of your application, you cannot ignore this topic. This boils down to the fact that my 09:00 o’clock is most likely different from your 09:00 o’clock.įor many applications this will be a very minor issue that can be safely ignored. In the day and age of remote work and distributed teams, a software developers must expect people in different time zones working with the same application, with the very same database. Today, I want to address another aspect of date and time: time zone information. I already wrote about universal considerations when dealing with date and time in an Access/VBA application and about formatting dates explicitly for a particular region. However, in our globally interconnected world you, as a software developer, must see date and time in the context of the regional customs of the user working with your application. By Philipp Stiefel, originally published Īt first thought, date and time might appear to be a very simple data point that can be treated as discrete values having the same meaning for everybody. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |