calculating unique time
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 18232
interpreted = N
texte = That is not the problem we originally talked about, therefore the new subject.At 13:01 Uhr 13.06.1998, bob wrote:You set the login time of a user like this:>logintime=[math]{{[time]}+{00:20:00}}+{[date]}[/math]Hmm... I don't think this will be reliable under any circumstances:[math]{date}[/math] returns the number of days since 00/00/000.[math]{time}[/math] returns the seconds since midnight.If you just add the two values, the result will merely depend on theseconds since midnight:Assume we have 729918 days and 64255 seconds now, we get729918 days + 64255 seconds = 794173Tomorrow we have 729919 days and let's say 20000 seconds:729919 days + 20000 seconds = 749919Effect: the time of tomorrow is older than the value of today! In factany hit tomorrow which occures before the corresponding today's time willbe lower - that is important if the user works around midnight...And here a never-can-be-example ;-)a user logs in today:729918 days + 64255 seconds = 794173and tomorrow, one second before he did today:729919 days + 64254 seconds = 794173Effect: the two results are identical, but there is actually one daydifference!Since WebCat has no (short) function to calculate seconds since the date00/00/0000, I do some sort of digit-shift to get reliable values:> currenthit=[math]{[date]}[/math]*100000> +[math]{[time]}[/math][/math](In clear text: days * 100000 + seconds)For example, a login today:729918 * 100000 = 72991800000 + 64255 = 729918064255and a login tomorrow, same time:729919 * 100000 = 72991900000 + 64255 = 729919064255Effect: tomorrows value is always higher than today's.Peter__________________________________________Peter Ostry - po@ostry.com - www.ostry.comOstry & Partner - Ostry Internet SolutionsAuhofstrasse 29 A-1130 Vienna Austriafon ++43-1-8777454 fax ++43-1-8777454-21
Associated Messages, from the most recent to the oldest:
That is not the problem we originally talked about, therefore the new subject.At 13:01 Uhr 13.06.1998, bob wrote:You set the login time of a user like this:>logintime=
[math]{{
[time]}+{00:20:00}}+{
[date]}[/math]Hmm... I don't think this will be reliable under any circumstances:
[math]{date}[/math] returns the number of days since 00/00/000.
[math]{time}[/math] returns the seconds since midnight.If you just add the two values, the result will merely depend on theseconds since midnight:Assume we have 729918 days and 64255 seconds now, we get729918 days + 64255 seconds = 794173Tomorrow we have 729919 days and let's say 20000 seconds:729919 days + 20000 seconds = 749919Effect: the time of tomorrow is older than the value of today! In factany hit tomorrow which occures before the corresponding today's time willbe lower - that is important if the user works around midnight...And here a never-can-be-example ;-)a user logs in today:729918 days + 64255 seconds = 794173and tomorrow, one second before he did today:729919 days + 64254 seconds = 794173Effect: the two results are identical, but there is actually one daydifference!Since WebCat has no (short) function to calculate seconds since the date00/00/0000, I do some sort of digit-shift to get reliable values:> currenthit=
[math]{
[date]}[/math]*100000> +
[math]{
[time]}[/math][/math](In clear text: days * 100000 + seconds)For example, a login today:729918 * 100000 = 72991800000 + 64255 = 729918064255and a login tomorrow, same time:729919 * 100000 = 72991900000 + 64255 = 729919064255Effect: tomorrows value is always higher than today's.Peter__________________________________________Peter Ostry - po@ostry.com - www.ostry.comOstry & Partner - Ostry Internet SolutionsAuhofstrasse 29 A-1130 Vienna Austriafon ++43-1-8777454 fax ++43-1-8777454-21
Peter Ostry
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:
case sensitivity in lookups (1997)
triggers.db (1999)
THANKS (1997)
setlineiems and UnitShip Cost (2000)
Emailer setup (1997)
RE: Questions To Answer (1997)
Exists? (1997)
method of payment (1997)
decrypt trouble - solved (2006)
hidden (phantom) file downloads (2000)
Menu to select product variations (1997)
Don't do this! (2003)
Multiple Sendmail Tags on One Page (2008)
Upload images to non DNA server (2004)
Question re: FlushDatabases (1997)
Passing WebCat data to SSL server (1997)
Conveting Characters to Graphics (1997)
Practice runs ? (1997)
(1997)
New WebDNA Solutions ... (1997)