Interpreting Date formats
Let’s say I have a DatePicker
control and I allow my US clients to type something like
"1/1"
in it and hit tab go to next control. So I will parse that date for them as “01/01/2014” and some more similar patterns. But they are all US-based so they are
standard format to describe opening schedules
I am working on a project in which I have to model opening schedules (eg a swimming pool is opened from 10:30am to 5pm on Tuesday from january to May. I try to fit this data in a csv and I started using a homemade format (the swimming pool example would be 1/1-30/5|Tu:10+30-17
).
standard format to describe opening schedules
I am working on a project in which I have to model opening schedules (eg a swimming pool is opened from 10:30am to 5pm on Tuesday from january to May. I try to fit this data in a csv and I started using a homemade format (the swimming pool example would be 1/1-30/5|Tu:10+30-17
).
Groovy date/time compare [closed]
Closed 9 years ago.
What is the preferable date-format used for designing APIs and storage
The date format should support different timezone and Daylight saving issues.