Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww

This WebDNA talk-list message is from

2002

It keeps the original formatting. numero = 45628
interpreted = N
texte = I think the results you see are valid. If one of the words you're matching is 2 then 400.2 is a match because 2 is surrounded on both sides by a word separator (space and period). Remember, You're looking at text, not numbers. The wbrk parameter affects the search string - not the values in the database field. You're correct that wo is not a valid comparison operator for numeric fields. In this case you should do this (I haven't tested, so it may need debugging, but it should get you started):[search db=products.db&GROUP1field=BLAH&GROUP2field=BLAH&eqGROUP1data=400.2&GROUP1type=num&eqGROUP2data=400.9&GROUP2type=num...]If you have a variable number of items you can set up the GROUPX parameters in a loop context.I hope this helps clear some things up and get's your signoff so you can get paid :>John.>I saw this in the archives a few days ago and now it has affected us ..>We have a search as follows>>[search db=products.db&woGROUPdata=400.2,400.9,2&GROUPword=ww&GROUPwbrk=,]>>This unfortunately returns groups as follows>>51.2>800.2>400.2>2>400.9>>As you can see the results are not as they should be .. When we take 2 out>of the search string this works perfectly. We have tried all sorts of other>delimiters and the results are the same.>>Can someone please confirm this and let us know when a fix is coming ?? Ken>mentioned in his response he knew of this a couple of years ago - WebDNA>cannot ignore it's internet delimiters when &wbrk= is specified in the>search ? Perhaps this could be squeezed into the 4.5.1 patch ?-- --------------------------------- John A. Hill Oak Hill SoftwareWebsite Development/Consulting john@oakhillsoftware.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:

Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Rob Marquardt 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (John Hill 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Dennis J. Bonsall, Jr. 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Dennis J. Bonsall, Jr. 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Alain Russell 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Stuart Tremain 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Scott Anderson 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Alain Russell 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (John Hill 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Rob Marquardt 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (John Hill 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Alain Russell 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (John Hill 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Bob Minor 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Tim Robinson 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (Alain Russell 2002)
Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww (John Hill 2002)

I think the results you see are valid. If one of the words you're matching is 2 then 400.2 is a match because 2 is surrounded on both sides by a word separator (space and period). Remember, You're looking at text, not numbers. The wbrk parameter affects the search string - not the values in the database field. You're correct that wo is not a valid comparison operator for numeric fields. In this case you should do this (I haven't tested, so it may need debugging, but it should get you started):[search db=products.db&GROUP1field=BLAH&GROUP2field=BLAH&eqGROUP1data=400.2&GROUP1type=num&eqGROUP2data=400.9&GROUP2type=num...]If you have a variable number of items you can set up the GROUPX parameters in a loop context.I hope this helps clear some things up and get's your signoff so you can get paid :>John.>I saw this in the archives a few days ago and now it has affected us ..>We have a search as follows>>[search db=products.db&woGROUPdata=400.2,400.9,2&GROUPword=ww&GROUPwbrk=,]>>This unfortunately returns groups as follows>>51.2>800.2>400.2>2>400.9>>As you can see the results are not as they should be .. When we take 2 out>of the search string this works perfectly. We have tried all sorts of other>delimiters and the results are the same.>>Can someone please confirm this and let us know when a fix is coming ?? Ken>mentioned in his response he knew of this a couple of years ago - WebDNA>cannot ignore it's internet delimiters when &wbrk= is specified in the>search ? Perhaps this could be squeezed into the 4.5.1 patch ?-- --------------------------------- John A. Hill Oak Hill SoftwareWebsite Development/Consulting john@oakhillsoftware.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/ John Hill

DOWNLOAD WEBDNA NOW!

Re: URGENT: NO BUG, woFIELDdata & FIELDword=ww

2002

Top Articles:

Related Readings: