Re: feature request-- [epoch]
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 55508
interpreted = N
texte = Here are some relative comments I found from another source: --begin comments Hi Norm, > In trying to work with the XML export from SourceForge, I see that > they store dates in the XML as seconds-since-1970. How quaint. > Anyway, this is actually a useful form sometimes. I wonder if it > makes sense to add: > > date:epoch-time() - returns the number of seconds since the epoch > (on Unix systems, the current epoch starts on Jan 1, 1970 at 00:00:00 GMT) > > date:epoch-time-to-date-time(int seconds) - returns a date-time for > a number of seconds > > date:date-time-to-epoch-time(string date-time) - does the inverse Currently, if you pass a date-time string to the date:seconds() function, then it gives you the number of seconds since 1970-01-01T00:00:00. So date:seconds() works as date:date-time-to-epoch-time() as above. What's more, if you call date:seconds() without an argument, it acts on the current date-time, so in fact date:seconds() without an argument is the same as date:epoch-time() as above. You can do date:epoch-time-to-date-time() by turning the number of seconds into a duration and adding that to the start of the epoch, as in: date:add('1970-01-01T00:00:00', date:duration($seconds)) Perhaps that's worth a shorthand -- possibly date:date-time() should have an optional argument, being a number of seconds since 1970-01-01T00:00:00 -- I'm not sure. There's an argument that date:seconds() shouldn't be overloaded, and shouldn't be tied to a particular epoch, especially the computer-oriented one of 1970-01-01T00:00:00 (Mike suggested Julian dates instead), but my feeling was (and is) that it's a common enough representation that it's worthwhile to support it specifically. For other epochs, you could use: date:seconds(date:difference($epoch, $date-time)) -- end coments -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE Eucalyptus Design <-Web Development (specializing in eCommerce), -> <-Graphic Design, and Pre-Press Consultation -> ADDRESS:> Donovan Brooke DBA Eucalyptus Design N2862 Summerville Park Rd. Lodi, WI 53555 PH:> 1.608.592.3567 Web:> http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Here are some relative comments I found from another source: --begin comments Hi Norm, > In trying to work with the XML export from SourceForge, I see that > they store dates in the XML as seconds-since-1970. How quaint. > Anyway, this is actually a useful form sometimes. I wonder if it > makes sense to add: > > date:epoch-time() - returns the number of seconds since the epoch > (on Unix systems, the current epoch starts on Jan 1, 1970 at 00:00:00 GMT) > > date:epoch-time-to-date-time(int seconds) - returns a date-time for > a number of seconds > > date:date-time-to-epoch-time(string date-time) - does the inverse Currently, if you pass a date-time string to the date:seconds() function, then it gives you the number of seconds since 1970-01-01T00:00:00. So date:seconds() works as date:date-time-to-epoch-time() as above. What's more, if you call date:seconds() without an argument, it acts on the current date-time, so in fact date:seconds() without an argument is the same as date:epoch-time() as above. You can do date:epoch-time-to-date-time() by turning the number of seconds into a duration and adding that to the start of the epoch, as in: date:add('1970-01-01T00:00:00', date:duration($seconds)) Perhaps that's worth a shorthand -- possibly date:date-time() should have an optional argument, being a number of seconds since 1970-01-01T00:00:00 -- I'm not sure. There's an argument that date:seconds() shouldn't be overloaded, and shouldn't be tied to a particular epoch, especially the computer-oriented one of 1970-01-01T00:00:00 (Mike suggested Julian dates instead), but my feeling was (and is) that it's a common enough representation that it's worthwhile to support it specifically. For other epochs, you could use: date:seconds(date:difference($epoch, $date-time)) -- end coments -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE Eucalyptus Design <-Web Development (specializing in eCommerce), -> <-Graphic Design, and Pre-Press Consultation -> ADDRESS:> Donovan Brooke DBA Eucalyptus Design N2862 Summerville Park Rd. Lodi, WI 53555 PH:> 1.608.592.3567 Web:> http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Donovan Brooke
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:
New global preference ... ??? (2000)
Beta List (1998)
PCS Frames (1997)
Calendar (1997)
WebCat2 - [format thousands] (1997)
searching twice on same field (1998)
Where's Cart Created ? (1997)
Emailer setup (1997)
Web*3 virtual hosting Webcatalog problem (1998)
Search results templates (1996)
What about that Cc and Bcc bug? (2000)
Closing databases (2003)
E-Mail Preferences in Admin Folder (1997)
Weird Math (2000)
math on date? (1997)
PSC recommends what date format yr 2000??? (1997)
Help formatting search results w/ table (1997)
[SQL] & ODBC on Mac - Reposted (2000)
[Webcat 2]Next (1997)
Upgrading old WebCat Database Files (1997)