numero = 28299
interpreted = N
texte = > >All triggers that execute once a day that executed correctly on > >2/28/2000 are now set to execute next on 3/1/2000. > >We have confirmed and apologize for this bug. Triggers should resume >correctly tomorrow. > >The bug has been identified and the fix will be rolled into the next >version. Obviously it is too late to get everyone a fix tonight, but >at least we can let everyone know what the limits of the problem are. >The bug only affects Triggers, and specifically on this leap day as >far as we know. It results from a special-case interaction between >WebDNA's nice clean Y2K-compliant code and the underlying operating >system's ANSI C date/time code (which tends to think it's year 100 >right now). > >WebDNA [math] and [date] work fine, as some on this list have already >reported. Calculations written using WebDNA accurately reflect the >correct leap days involving 100-year and 400-year cycles.Hmm I am not so sure. On one box here the following code gave the Year as 2070, Micheal O Shea Email:micheal@com4u.ch com4u.ch http://www.com4u.ch Breitistrasse 7B PGP key available upon request. CH-5506 Maegenwil Tel: +41 62 896 46 26 Switzerland------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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
Associated Messages, from the most recent to the oldest:
Re: Leap Day Triggers? -confirmation- (Michael O Shea 2000)
> >All triggers that execute once a day that executed correctly on > >2/28/2000 are now set to execute next on 3/1/2000. > >We have confirmed and apologize for this bug. triggers should resume >correctly tomorrow. > >The bug has been identified and the fix will be rolled into the next >version. Obviously it is too late to get everyone a fix tonight, but >at least we can let everyone know what the limits of the problem are. >The bug only affects triggers, and specifically on this leap day as >far as we know. It results from a special-case interaction between >WebDNA's nice clean Y2K-compliant code and the underlying operating >system's ANSI C date/time code (which tends to think it's year 100 >right now). > >WebDNA [math] and [date] work fine, as some on this list have already >reported. Calculations written using WebDNA accurately reflect the >correct leap days involving 100-year and 400-year cycles.Hmm I am not so sure. On one box here the following code gave the Year as 2070, Micheal O Shea Email:micheal@com4u.ch com4u.ch http://www.com4u.ch Breitistrasse 7B PGP key available upon request. CH-5506 Maegenwil Tel: +41 62 896 46 26 Switzerland------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .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 Michael O Shea
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...