Re: [WebDNA] Storing time in 24hr format

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113051
interpreted = N
texte = 639 --001a113d4f28b49ed7053e4bf9ef Content-Type: text/plain; charset=UTF-8 Excellent point Donovan. I will need to do that for the time card function. Right now I am only storing their shift start and to show on a list so everyone knows when each other works. Thank you! Dale On Fri, Oct 7, 2016 at 3:02 PM, Donovan Brooke wrote: > You want seconds since epoch. > > Sincerely, > Donovan > > > > On Oct 7, 2016, at 2:40 PM, dale wrote: > > > 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 > > --------------------------------------------------------- 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 > > --------------------------------------------------------- > 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 > --001a113d4f28b49ed7053e4bf9ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Excellent point Donovan.

I will need to= do that for the time card function. Right now I am only storing their shif= t start and to show on a list so everyone knows when each other works.=C2= =A0

Thank you!

Dale=C2=A0=

On Fr= i, Oct 7, 2016 at 3:02 PM, Donovan Brooke <dbrooke@euca.us> wr= ote:
You want seconds since epoch.

Sincerely,
Donovan



On Oct 7, 2016, at 2:40 PM, dale <d= therio@gmail.com> wrote:

> 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 en= d 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 r= ecommend 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 usin= g this site as a time clock to replace the system we are currently using. T= hese punch-in times and dates will be stored in another database. The major= ity of the techs start work about 6:00 pm and work until 3:00am.
>
> The above data will also include location information from their mobil= e devices (they all work on various lots, so location information is import= ant).
>
> 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.web= dna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--------------------------------------------------------- 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 --001a113d4f28b49ed7053e4bf9ef-- . 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)
639 --001a113d4f28b49ed7053e4bf9ef Content-Type: text/plain; charset=UTF-8 Excellent point Donovan. I will need to do that for the time card function. Right now I am only storing their shift start and to show on a list so everyone knows when each other works. Thank you! Dale On Fri, Oct 7, 2016 at 3:02 PM, Donovan Brooke wrote: > You want seconds since epoch. > > Sincerely, > Donovan > > > > On Oct 7, 2016, at 2:40 PM, dale wrote: > > > 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 > > --------------------------------------------------------- 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 > > --------------------------------------------------------- > 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 > --001a113d4f28b49ed7053e4bf9ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Excellent point Donovan.

I will need to= do that for the time card function. Right now I am only storing their shif= t start and to show on a list so everyone knows when each other works.=C2= =A0

Thank you!

Dale=C2=A0=

On Fr= i, Oct 7, 2016 at 3:02 PM, Donovan Brooke <dbrooke@euca.us> wr= ote:
You want seconds since epoch.

Sincerely,
Donovan



On Oct 7, 2016, at 2:40 PM, dale <d= therio@gmail.com> wrote:

> 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 en= d 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 r= ecommend 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 usin= g this site as a time clock to replace the system we are currently using. T= hese punch-in times and dates will be stored in another database. The major= ity of the techs start work about 6:00 pm and work until 3:00am.
>
> The above data will also include location information from their mobil= e devices (they all work on various lots, so location information is import= ant).
>
> 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.web= dna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--------------------------------------------------------- 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 --001a113d4f28b49ed7053e4bf9ef-- . 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:

More on the email templates (1997) case number with spaces. (2000) WebMerchant 3.0 for Mac shipping now (1998) [TaxableTotal] - not working with AOL and IE (1997) Card clearance, problems - solutions? (1997) RE: Re:Signal Raised (1997) date tag not interpreted (2000) Deleting Orders (1997) If Empty ? (1997) update on wn searching (1997) database performance/design question (2000) Re:quit command on NT (1997) WebCat editing, SiteGuard & SiteEdit (1997) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) Time Display from Database (1997) Cart Already Submitted (2003) Bug? (1997) PIXO support (1997) WebCat B13 Mac CGI -- Frames question (1997) Pulling Captions from JPGs (2003)