Re: Search or delete (or date or time) has bugs ...
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 16977
interpreted = N
texte = >>[search >db=this.db&ledeleteDatedatarq=[date]&ledeleteTimedatarq=[time]&deleteDatetyp >e=date] >> >>is failing to retrieve the proper records. Instead, it actually looks like >WebCat is retrieving records that do not match all the parameters (even >though I've clearly used rq to force all parameters to match), or that >it's retrieving a different set of records each time. >> >>What's going on here ... ? >> >>Am I missing something very simple and obvious here, or does WebCatalog >have some real problems dealing with date comparisons? >> > >Hi Ken, > >I'm not completely familiar w/ WebCat yet, so please pardon my ignorance if >this is irrelevant, but I had a similar problem which I solved by entering >the date & time as a single value: > >[date]@[time] > >For some reason, this was the only way I could get WC to differentiate >between the records I wanted to delete or edit, & the ones I didn't want it >to touch. > >Hope this can help... Thanks Tamara,The reason your solution may have worked is because it effectively forces WebCatalog to consider both the date and the time field as a single field ... and also because that single field is not defined as a date field, so that means WebCatalog is comparing it as a text field.I actually got rid of all my time fields to see if they were contributing to the problem, and they were not. In my case, with only the deleteDate field as a single field in the search string, and no other search parameters whatsoever (except for deleteDateType=date), the results are still wrong.But that may be because I'm telling WebCatalog to look at those values as dates ...Unfortunately, that's exactly what I'm supposed to be doing, yet the search fails. The docs say: All sorting, summaries, and comparisons work correctly when you tell WebCatalog which fields are to be treated as dates.But obviously this is not true, and in fact it may actually be impossible to rely on date comparisons until this is fixed.Of course, there's always a work-around, such as storing the dates in the database in YYYY/MM/DD format, which allows them to be compared as text instead of as dates. But that's just a band-aid, not a solution to the real problem ...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:
>>[search >db=this.db&ledeleteDatedatarq=
[date]&ledeleteTimedatarq=
[time]&deleteDatetyp >e=date] >> >>is failing to retrieve the proper records. Instead, it actually looks like >WebCat is retrieving records that do not match all the parameters (even >though I've clearly used rq to force all parameters to match), or that >it's retrieving a different set of records each time. >> >>What's going on here ... ? >> >>Am I missing something very simple and obvious here, or does WebCatalog >have some real problems dealing with date comparisons? >> > >Hi Ken, > >I'm not completely familiar w/ WebCat yet, so please pardon my ignorance if >this is irrelevant, but I had a similar problem which I solved by entering >the date & time as a single value: > >
[date]@
[time] > >For some reason, this was the only way I could get WC to differentiate >between the records I wanted to delete or edit, & the ones I didn't want it >to touch. > >Hope this can help... Thanks Tamara,The reason your solution may have worked is because it effectively forces WebCatalog to consider both the date and the time field as a single field ... and also because that single field is not defined as a date field, so that means WebCatalog is comparing it as a text field.I actually got rid of all my time fields to see if they were contributing to the problem, and they were not. In my case, with only the deleteDate field as a single field in the search string, and no other search parameters whatsoever (except for deleteDateType=date), the results are still wrong.But that may be because I'm telling WebCatalog to look at those values as dates ...Unfortunately, that's exactly what I'm supposed to be doing, yet the search fails. The docs say: All sorting, summaries, and comparisons work correctly when you tell WebCatalog which fields are to be treated as dates.But obviously this is not true, and in fact it may actually be impossible to rely on date comparisons until this is fixed.Of course, there's always a work-around, such as storing the dates in the database in YYYY/MM/DD format, which allows them to be compared as text instead of as dates. But that's just a band-aid, not a solution to the real problem ...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:
Country & Ship-to address & other fields ? (1997)
$Replace with [founditems] (1997)
Re(2): Re(4): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (1998)
max page views Mac can handle (1999)
ShipCosts database (1997)
[WebDNA] plupload ? (2012)
WebCat and WebTV (1997)
Sending Email (2004)
[OT]: BBEdit grep (2003)
Generating Searches on the fly? (1999)
problems with 2 tags (1997)
New Command prefs ... (1997)
Closing Databases (1998)
Emailer port change (1997)
Multiple Ad databases? (1997)
Logging purchases (1997)
Beta (?) version of WebCatalog 2.1 (1998)
Re:2nd WebCatalog2 Feature Request (1996)
WebCat2 beta 11 - new prefs ... (1997)
Too many tabs in order file? (1998)