Re: date format (another question)

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 26798
interpreted = N
texte = >I still am conflicted about using the different methods because they each >seem to have advantages and disadvantages. That's why Bob's suggestion makes the most sense -- use both. Better yet, suse my techinqie in one forls, and use 3 additional fields -- MM, DD and YYYY. Add a Weekday field too if you have to search by day of the week.>I think an answer to the performance question might sway things, but >I suspect that the performance hit is minimal.It is probably best if you do not make assumptions like this. I have proven this issue to be so serious -- in some situations -- as to make webcat totally useless for all practical purposes.If you want to prove it yourself, try searching a 700,000-record db, each record having a mm/dd/yyyy formatted date value. Do your search for a date occurring in between the two date values in your search context. You'll see that performance slows to a crawl -- with only ONE HIT to the server in a test environment. Now multiply that dozens of times to simulate a busy website in the real world, then tell me the performance hit is 'minimal' ...Th fact is, the performance hit is *huge* when you have hundreds of thousands of records with formatted date values in them, and it is compounded when you have a busy website. I would not have developed my days since 0000 date storage/searching techniques if webcat could have handled it otherwise ...================================ Kenneth Grome, WebDNA Consultant 808-737-6499, http://webdna.net ================================------------------------------------------------------------- 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:

    
  1. Re: date format (another question) (Kenneth Grome 2000)
  2. Re: date format (another question) (Dave MacLeay 2000)
  3. Re: date format (another question) (Joseph D'Andrea 2000)
  4. Re: date format (another question) (Kenneth Grome 2000)
  5. Re: date format (another question) (Eric Ridgley 2000)
  6. Re: date format (another question) (Joseph D'Andrea 2000)
  7. Re: date format (another question) (Dale Therio 2000)
  8. Re: date format (another question) (Bob Minor 2000)
  9. Re: date format (another question) (Joseph D'Andrea 2000)
  10. Re: date format (another question) (Dale Therio 2000)
>I still am conflicted about using the different methods because they each >seem to have advantages and disadvantages. That's why Bob's suggestion makes the most sense -- use both. Better yet, suse my techinqie in one forls, and use 3 additional fields -- MM, DD and YYYY. Add a Weekday field too if you have to search by day of the week.>I think an answer to the performance question might sway things, but >I suspect that the performance hit is minimal.It is probably best if you do not make assumptions like this. I have proven this issue to be so serious -- in some situations -- as to make webcat totally useless for all practical purposes.If you want to prove it yourself, try searching a 700,000-record db, each record having a mm/dd/yyyy formatted date value. Do your search for a date occurring in between the two date values in your search context. You'll see that performance slows to a crawl -- with only ONE HIT to the server in a test environment. Now multiply that dozens of times to simulate a busy website in the real world, then tell me the performance hit is 'minimal' ...Th fact is, the performance hit is *huge* when you have hundreds of thousands of records with formatted date values in them, and it is compounded when you have a busy website. I would not have developed my days since 0000 date storage/searching techniques if webcat could have handled it otherwise ...================================ Kenneth Grome, WebDNA Consultant 808-737-6499, http://webdna.net ================================------------------------------------------------------------- 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 Kenneth Grome

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:

BUG REPORT: Delete context ignores max parameter (1998) selectively replacing records within a [founditems] (2000) Globals Permissions (2003) [isfile] ? (1997) Webcat table size. (2001) problems with 2 tags (1997) Fun with dates (1997) Calculate UnitShipCost in Formulas.db (1999) Dates (1995) Dumb Question about Docs (1997) Server crash (1997) WebCatalog and WebMerchant reviewed by InfoWorld (1997) [HIDEIF] inside [FOUNDITEM] (1997) RE: [WebDNA] directory protection questions (2008) Snake Bites (1997) Pithy questions on webcommerce & siteedit (1997) URL for Discussion Archive (1997) GuestBook example (1997) Template not found error messages (1997) unique ascending numbers (2003)