Re: Date search bug?

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17705
interpreted = N
texte = Hi everyone,While I still recommend using the date formatting suggestions I made available a few days ago, there may be some of you who really don't want to mess around with a change-over like that ... so here's some CRITICAL information that may help to make your existing date range searches work properly:The following exchange occurred between myself and Grant after I sent him some files that demonstrated the date range search bug I discovered:>>Have you or anyone tracked down the date bug with those files I sent you a >>couple days ago? > >It appears to be the comma between the dates in the range. I removed the >comma and got much better-looking results. Sorry about the delay and the >misinformation.Basically, what this means is that the HTML docs are wrong -- you should NOT use a comma to separate the two values in a date range search. Instead, you should try using a blank space (or possibly a plus sign) to separate the two date values.I still don't know whether or not the earliest date value in a date range search needs to be listed first -- or if the order makes no difference. But putting the earliest date value first has eliminated problems reported with some earlier versions of WebCatalog, so it's probably still a good idea to continue that practice, just to be on the safe side ... :)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Associated Messages, from the most recent to the oldest:

    
  1. Re: Date search bug? (Kenneth Grome 1998)
Hi everyone,While I still recommend using the date formatting suggestions I made available a few days ago, there may be some of you who really don't want to mess around with a change-over like that ... so here's some CRITICAL information that may help to make your existing date range searches work properly:The following exchange occurred between myself and Grant after I sent him some files that demonstrated the date range search bug I discovered:>>Have you or anyone tracked down the date bug with those files I sent you a >>couple days ago? > >It appears to be the comma between the dates in the range. I removed the >comma and got much better-looking results. Sorry about the delay and the >misinformation.Basically, what this means is that the HTML docs are wrong -- you should NOT use a comma to separate the two values in a date range search. Instead, you should try using a blank space (or possibly a plus sign) to separate the two date values.I still don't know whether or not the earliest date value in a date range search needs to be listed first -- or if the order makes no difference. But putting the earliest date value first has eliminated problems reported with some earlier versions of WebCatalog, so it's probably still a good idea to continue that practice, just to be on the safe side ... :)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net 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:

Emailer Set Up (1997) Grep Question - MAY NEVER BE SOLVED (2003) WebCat2b13MacPlugin - nested [xxx] contexts (1997) syntax question, not in online refernce (1997) StoreBuilder ADD 2 CART redirects to default.tpl - PLEASESTOP THIS! (2002) [Sum] function? (1997) template not found error (1998) carrying values forward (1998) wish list (2002) Snake Bites (1997) &fieldsdir=ra truely random?? (2000) osx 10.3,webcat,permissions (2004) Multiple Pulldowns (1997) Where's Cart Created ? (1997) RE: [WebDNA] AJAX module (2012) docs for WebCatalog2 (1997) grep for search, not replace (2002) Shownext on AOL (2003) Thanks for tips, more quest (1997) [WebDNA] Poll: Discussion Forum (2009)