Re: [lookup] [search] Issue
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 63120
interpreted = N
texte = Bingo! At sometime, the contents of the field in the db had been changed to lowercase - so a simple [lowercase][word][/lowercase] did the trick. Is there a way to tell a [lookup] to ignore case totally? Mark. On 22 Sep 2005, at 14:44, Brian Fries wrote: > Generally if a search with an "eq" comparison works and a lookup > doesn't, the problem is case-sensitivity. The search will match BOB > to bob, but the lookup won't. > > - Brian > > On Sep 22, 2005, at 1:54 AM, Mark Derrick wrote: > > >> The database has no empty fields or duplicates, and if I put >> quotes around [CUSTOMID] I get just one set of quotes. >> If I put quotes around the [lookup], and for example the [search] >> line returns 4 results, then I get four pairs of empty quotes >> displayed by the [lookup] line. >> >> The [ListWords] is returning the correct results, and even if I >> enter a variable directly into the lookup, it still refuses to >> find a record in the db file. >> >> The odd thing, is that this used to work fine, it just stopped a >> while ago - and I've been spending my time since then trying to >> figure out why. >> >> Mark. >> >> >> On 21 Sep 2005, at 18:33, devaulw@onebox.com wrote: >> >> >>> Is it possible you have two records with the same customid and >>> one has a blank for the lookup field? Put quotes around >>> [CUSTOMNAME] in the search results to see if you get one or more >>> sets of quotes. >>> Bill >>> >>> -----Original Message----- >>> From: Mark Derrick
>>> Sent: Wed, 21 Sep 2005 17:50:36 +0100 >>> To: "WebDNA Talk" >>> Subject: Re: [lookup] [search] Issue >>> >>> Sorry, I should have mentioned that this is within a [ListWords] >>> context. >>> >>> I've run these two lines on the same page, and the data is only >>> returned by the [search] line. >>> >>> Mark. >>> >>> >>> On 21 Sep 2005, at 15:50, nitai@computeroil.com wrote: >>> >>> >>> >>>> Change the [word] to something else. This looks to me like a >>>> reserved word for WebDNA. >>>> >>>> Nitai >>>> >>>> -- >>>> >>>> >>>> >>>> >>>>> -----Original Message----- >>>>> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On >>>>> Behalf Of >>>>> Mark Derrick >>>>> Sent: Mittwoch, 21. September 2005 16:45 >>>>> To: WebDNA Talk >>>>> Subject: [lookup] [search] Issue >>>>> >>>>> I've been staring at this for too long now, and can't see the wood >>>>> for the trees. >>>>> Can anyone see why the [search] works, but the [lookup] doesn't? >>>>> >>>>> [LOOKUP db=^databases/customnames.db&value=[word] >>>>> &lookInField=CUSTOMID&returnField=CUSTOMNAME] >>>>> >>>>> [search db=^databases/customnames.db&eqCUSTOMIDdatarq=[word]] >>>>> [founditems][CUSTOMNAME][/founditems][/search] >>>>> >>>>> Thanks. >>>>> > > > ------------------------------------------------------------- > 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 digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- 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:
Bingo! At sometime, the contents of the field in the db had been changed to lowercase - so a simple [lowercase][word][/lowercase] did the trick. Is there a way to tell a [lookup] to ignore case totally? Mark. On 22 Sep 2005, at 14:44, Brian Fries wrote: > Generally if a search with an "eq" comparison works and a lookup > doesn't, the problem is case-sensitivity. The search will match BOB > to bob, but the lookup won't. > > - Brian > > On Sep 22, 2005, at 1:54 AM, Mark Derrick wrote: > > >> The database has no empty fields or duplicates, and if I put >> quotes around [CUSTOMID] I get just one set of quotes. >> If I put quotes around the [lookup], and for example the [search] >> line returns 4 results, then I get four pairs of empty quotes >> displayed by the [lookup] line. >> >> The [listwords] is returning the correct results, and even if I >> enter a variable directly into the lookup, it still refuses to >> find a record in the db file. >> >> The odd thing, is that this used to work fine, it just stopped a >> while ago - and I've been spending my time since then trying to >> figure out why. >> >> Mark. >> >> >> On 21 Sep 2005, at 18:33, devaulw@onebox.com wrote: >> >> >>> Is it possible you have two records with the same customid and >>> one has a blank for the lookup field? Put quotes around >>> [CUSTOMNAME] in the search results to see if you get one or more >>> sets of quotes. >>> Bill >>> >>> -----Original Message----- >>> From: Mark Derrick >>> Sent: Wed, 21 Sep 2005 17:50:36 +0100 >>> To: "WebDNA Talk" >>> Subject: Re: [lookup] [search] Issue >>> >>> Sorry, I should have mentioned that this is within a [listwords] >>> context. >>> >>> I've run these two lines on the same page, and the data is only >>> returned by the [search] line. >>> >>> Mark. >>> >>> >>> On 21 Sep 2005, at 15:50, nitai@computeroil.com wrote: >>> >>> >>> >>>> Change the [word] to something else. This looks to me like a >>>> reserved word for WebDNA. >>>> >>>> Nitai >>>> >>>> -- >>>> >>>> >>>> >>>> >>>>> -----Original Message----- >>>>> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On >>>>> Behalf Of >>>>> Mark Derrick >>>>> Sent: Mittwoch, 21. September 2005 16:45 >>>>> To: WebDNA Talk >>>>> Subject: [lookup] [search] Issue >>>>> >>>>> I've been staring at this for too long now, and can't see the wood >>>>> for the trees. >>>>> Can anyone see why the [search] works, but the [lookup] doesn't? >>>>> >>>>> [LOOKUP db=^databases/customnames.db&value=[word] >>>>> &lookInField=CUSTOMID&returnField=CUSTOMNAME] >>>>> >>>>> [search db=^databases/customnames.db&eqCUSTOMIDdatarq=[word]] >>>>> [founditems][CUSTOMNAME][/founditems][/search] >>>>> >>>>> Thanks. >>>>> > > > ------------------------------------------------------------- > 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 digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- 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/
Mark Derrick
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:
Error Messages Returned to User (1997)
[WebDNA] WebDNA7 url plus get? (2011)
Rhapsody? (1997)
Setting variables. (1998)
WebDNA Speed Test (2008)
Security Hole (1998)
StoreBuilder UPS/XML code question ... (2003)
Digest for 4/18/97 (1997)
REDIRECT MULTIPLE RESULTS (2000)
[append] and SSL (1997)
Re2: frames & carts (1997)
Form Data, Back Button and 6.0.1 Patch (2005)
Saving/Looking Up customer numbers (1998)
Zip Code Lookups (1999)
Cart # Starting at 1000 (2000)
Pithy questions on webcommerce & siteedit (1997)
WebCat2b13MacPlugin - nested [xxx] contexts (1997)
I give up!! (1997)
WebCat2 Append problem (B14Macacgi) (1997)
Properly coded search fails ... (2003)