[WebDNA] Storing time in 24hr format

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113049
interpreted = N
texte = 637 --001a113d5ece95a491053e4b96e0 Content-Type: text/plain; charset=UTF-8 Hi all, I am going to be storing shirt start and shift end times in a db. For now it is simply showing when the technicians are scheduled to start and end their shift as well as when their lunch time starts. I'm not looking for code, only your thoughts on the smartest/most flexible way to save the time. For doing any calculations I may need or want to do later, would you recommend storing the time as: 6:00 06:00 0600 I believe the later is the correct representation of 24 hour time. And probably would be easier to do any math on the numbers. For a further revision, I have been asked to look into eventually using this site as a time clock to replace the system we are currently using. These punch-in times and dates will be stored in another database. The majority of the techs start work about 6:00 pm and work until 3:00am. The above data will also include location information from their mobile devices (they all work on various lots, so location information is important). Thank you for your thoughts. Dale --001a113d5ece95a491053e4b96e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

I am going to be storing shirt = start and shift end times in a db. For now it is simply showing when the te= chnicians are scheduled to start and end their shift as well as when their = lunch time starts.

I'm not looking for code, o= nly your thoughts on the smartest/most flexible way to save the time.

For doing any calculations I may need or want to do= later, would you recommend storing the time as:

6= :00
06:00
0600


= I believe the later is the correct representation of 24 hour time. And prob= ably would be easier to do any math on the numbers.=C2=A0


For a further revision, I have been asked to look in= to eventually using this site as a time clock to replace the system we are = currently using. These punch-in times and dates will be stored in another d= atabase. The majority of the techs start work about 6:00 pm and work until = 3:00am.

The above data will also include location = information from their mobile devices (they all work on various lots, so lo= cation information is important).=C2=A0

Thank you = for your thoughts.

Dale
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --001a113d5ece95a491053e4b96e0-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Storing time in 24hr format (dale 2016)
  2. Re: [WebDNA] Storing time in 24hr format (Donovan Brooke 2016)
  3. Re: [WebDNA] Storing time in 24hr format (christophe.billiottet@webdna.us 2016)
  4. Re: [WebDNA] Storing time in 24hr format (Stephen Braun 2016)
  5. Re: [WebDNA] Storing time in 24hr format (Kenneth Grome 2016)
  6. Re: [WebDNA] Storing time in 24hr format (dale 2016)
  7. Re: [WebDNA] Storing time in 24hr format (Donovan Brooke 2016)
  8. [WebDNA] Storing time in 24hr format (dale 2016)
637 --001a113d5ece95a491053e4b96e0 Content-Type: text/plain; charset=UTF-8 Hi all, I am going to be storing shirt start and shift end times in a db. For now it is simply showing when the technicians are scheduled to start and end their shift as well as when their lunch time starts. I'm not looking for code, only your thoughts on the smartest/most flexible way to save the time. For doing any calculations I may need or want to do later, would you recommend storing the time as: 6:00 06:00 0600 I believe the later is the correct representation of 24 hour time. And probably would be easier to do any math on the numbers. For a further revision, I have been asked to look into eventually using this site as a time clock to replace the system we are currently using. These punch-in times and dates will be stored in another database. The majority of the techs start work about 6:00 pm and work until 3:00am. The above data will also include location information from their mobile devices (they all work on various lots, so location information is important). Thank you for your thoughts. Dale --001a113d5ece95a491053e4b96e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

I am going to be storing shirt = start and shift end times in a db. For now it is simply showing when the te= chnicians are scheduled to start and end their shift as well as when their = lunch time starts.

I'm not looking for code, o= nly your thoughts on the smartest/most flexible way to save the time.

For doing any calculations I may need or want to do= later, would you recommend storing the time as:

6= :00
06:00
0600


= I believe the later is the correct representation of 24 hour time. And prob= ably would be easier to do any math on the numbers.=C2=A0


For a further revision, I have been asked to look in= to eventually using this site as a time clock to replace the system we are = currently using. These punch-in times and dates will be stored in another d= atabase. The majority of the techs start work about 6:00 pm and work until = 3:00am.

The above data will also include location = information from their mobile devices (they all work on various lots, so lo= cation information is important).=C2=A0

Thank you = for your thoughts.

Dale
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --001a113d5ece95a491053e4b96e0-- . dale

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Passing along data (2000) Sendmail Woes (2002) Protecting databases (1999) Mac Scheduling (1998) Protecting Files (how to display vs. present a link to (2005) WebCat2 - Getting to the browser's username/password data (1997) using french characters (2000) PHP vs WebDNA question --calling all php gurus (2004) Nitro plugin? (1998) Country & Ship-to address & other fields ? (1997) [WebDNA] Solution to dynamic error pages on Apache (2011) 'does not contain' operator needed ... (1997) Problems adding stuff to the shopping cart. (1997) Problems getting parameters passed into email. (1997) RequiredFields template (1997) Looping Search (2006) RE: Include (1998) Email Formatting (1998) Problems with upload / WebCat (1998) RAM problems, [appendfile] problems (1998)