Re: [WebDNA] Displaying time specific records

This WebDNA talk-list message is from

2010

It keeps the original formatting. numero = 105938
interpreted = N
texte = --Apple-Mail-22--126754974Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=iso-8859-1Or instead of storing in two fields you could have one called datetimeThen store this value as [math]{[date %y/%m/%d]}[/math].[format =.5d][math]{[Date %X]}[/math][/format]which would come out as something like734453.45355or=20734453.00001 for 1 second past midnightThen you would just need to search for=20&lsdatetimedatarq=3D[math]{[date %y/%m/%d]}[/math].[format =.5d][math]{[Date %X]}[/math][/format]&datetimetype=3DnumNot sure it's worth the extra hassle instead of having two fairly simple =fieldsTCOn 12 Nov 2010, at 12:27, Steve Raslevich wrote:> Tom,>=20> Would perhaps creating a trigger to occur everyday at 2pm to search =for any press release scheduled and if found then post?=20>=20> Steve>=20> Tom Duke wrote:>>=20>> Hi all,>>=20>> Wondering how people deal with time specific records. =C2 I.e. a =press release that can only be shown after 2pm on a specific day. =C2 =The time restriction only applies on the day the press release is =issued.>>=20>> Currently I store the dates and times in separate fields - should I =be looking at using a Unix style timestamp or 'seconds since' - or is =there an easier way.>>=20>> Take care>> - Tom>>=20>>=20>=20> --=20> Steve Raslevich> President/CEO> Northern Sound & Light, Inc.> 11 Shingiss Street> McKees Rocks, Pennsylvania 15136>=20> Phone: (412) 331-1000> Fax: (412) 331-1035>=20> http://www.northernsound.net>=20> -------------------------------------------------------------------> This Email and any files transmitted with it contain confidential, =non-public information intended solely for the use of the individual to =whom or the entity to which they are addressed. Unauthorized use, =reproduction, distribution or communication of this message or any =information contained or attached to this message is strictly prohibited =and may be unlawful.=20>=20> If you have received this email in error please notify the sender =immediately by e-mail or contact Northern Sound & Light at =frontdesk@northernsound.net or (412) 331-1000.> ---------------------------------------------------------------------Apple-Mail-22--126754974Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=iso-8859-1Or =instead of storing in two fields you could have one called =datetime

Then store this value as [math]{[date =%y/%m/%d]}[/math].[format .5d][math]{[Date =%X]}[/math][/format]

which would =come out as something =like

734453.45355

or&nbs=p;

734453.00001 for 1 second past =midnight

Then you would just need to search =for

&lsdatetimedatarq=3D[math]{[date =%y/%m/%d]}[/math].[format .5d][math]{[Date =%X]}[/math][/format]&datetimetype=3Dnum

<=/div>

Not sure it's worth the extra hassle instead of having two =fairly simple =fields

On 12 Nov 2010, at 12:27, Steve Raslevich wrote:

Tom,

Would perhaps creating a trigger to occur everyday at 2pm to search forany press release scheduled and if found then post?

Steve

Tom Duke wrote:
Hi all,

Wondering how people deal with time specific records. =C2 I.e.= apress release that can only be shown after 2pm on a specific day. ==C2 The time restriction only applies on the day the press release isissued.

Currently I store the dates and times in separate fields -should I be looking at using a Unix style timestamp or 'seconds since'- or is there an easier way.

Take care

- Tom
--=20Steve RaslevichPresident/CEONorthern Sound & Light, Inc.11 Shingiss StreetMcKees Rocks, Pennsylvania 15136Phone: (412) 331-1000Fax: (412) 331-1035http://www.northernsound.net-------------------------------------------------------------------This Email and any files transmitted with it contain confidential, =non-public information intended solely for the use of the individual to =whom or the entity to which they are addressed. Unauthorized use, =reproduction, distribution or communication of this message or any =information contained or attached to this message is strictly prohibited =and may be unlawful.=20If you have received this email in error please notify the sender =immediately by e-mail or contact Northern Sound & Light at frontdesk@northernsound.net or (412) 331-1000.=-------------------------------------------------------------------

=--Apple-Mail-22--126754974-- Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Displaying time specific records (Tom Duke 2010)
RE: [WebDNA] Displaying time specific records ("Olin Lagon" 2010)
Re: [WebDNA] Displaying time specific records (Tom Duke 2010)
Re: [WebDNA] Displaying time specific records (Kenneth Grome 2010)
Re: [WebDNA] Displaying time specific records (Toby Cox 2010)
Re: [WebDNA] Displaying time specific records (Steve Raslevich 2010)
[WebDNA] Displaying time specific records (Tom Duke 2010)

--Apple-Mail-22--126754974Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=iso-8859-1Or instead of storing in two fields you could have one called datetimeThen store this value as [math]{[date %y/%m/%d]}[/math].[format =.5d][math]{[Date %X]}[/math][/format]which would come out as something like734453.45355or=20734453.00001 for 1 second past midnightThen you would just need to search for=20&lsdatetimedatarq=3D[math]{[date %y/%m/%d]}[/math].[format =.5d][math]{[Date %X]}[/math][/format]&datetimetype=3DnumNot sure it's worth the extra hassle instead of having two fairly simple =fieldsTCOn 12 Nov 2010, at 12:27, Steve Raslevich wrote:> Tom,>=20> Would perhaps creating a trigger to occur everyday at 2pm to search =for any press release scheduled and if found then post?=20>=20> Steve>=20> Tom Duke wrote:>>=20>> Hi all,>>=20>> Wondering how people deal with time specific records. =C2 I.e. a =press release that can only be shown after 2pm on a specific day. =C2 =The time restriction only applies on the day the press release is =issued.>>=20>> Currently I store the dates and times in separate fields - should I =be looking at using a Unix style timestamp or 'seconds since' - or is =there an easier way.>>=20>> Take care>> - Tom>>=20>>=20>=20> --=20> Steve Raslevich> President/CEO> Northern Sound & Light, Inc.> 11 Shingiss Street> McKees Rocks, Pennsylvania 15136>=20> Phone: (412) 331-1000> Fax: (412) 331-1035>=20> http://www.northernsound.net>=20> -------------------------------------------------------------------> This Email and any files transmitted with it contain confidential, =non-public information intended solely for the use of the individual to =whom or the entity to which they are addressed. Unauthorized use, =reproduction, distribution or communication of this message or any =information contained or attached to this message is strictly prohibited =and may be unlawful.=20>=20> If you have received this email in error please notify the sender =immediately by e-mail or contact Northern Sound & Light at =frontdesk@northernsound.net or (412) 331-1000.> ---------------------------------------------------------------------Apple-Mail-22--126754974Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=iso-8859-1Or =instead of storing in two fields you could have one called =datetime