Re: URGENT: PERHAPS A BUG, woFIELDdata & FIELDword=ww

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 45629
interpreted = N
texte = That would be ok but the search string also contains a whole bunch of other conditions .. As you will see below:&eqPROD_VISIBLEdatarq=T&nePRICEdatarq=[BLANK]&nePROD_NAMEdatarq=[BLANK]&dePR OD_SPECIALsort=1&asSKUsort=2&allhit=1&startat=[startat]&max=[max_found_items ]So I need to be able to specify FIELDSdatarq on the group .. But then it won't work with more than one on the same field.Just for reference - this would be the entire search string .. db=/db/products.db&GROUP1fields=PRODUCT_GROUP&eqGROUP1data=400.7&GROUP1type= number&GROUP2fields=PRODUCT_GROUP&eqGROUP2data=400.9&GROUP2type=number&GROUP 3fields=PRODUCT_GROUP&eqGROUP3data=400.3&GROUP3type=number&GROUP4fields=PROD UCT_GROUP&eqGROUP4data=400.6&GROUP4type=number&GROUP5fields=PRODUCT_GROUP&eq GROUP5data=400.4&GROUP5type=number&GROUP6fields=PRODUCT_GROUP&eqGROUP6data=4 00.2&GROUP6type=number&GROUP7fields=PRODUCT_GROUP&eqGROUP7data=400.8&GROUP7t ype=number&GROUP8fields=PRODUCT_GROUP&eqGROUP8data=18&GROUP8type=number&GROU P9fields=PRODUCT_GROUP&eqGROUP9data=2&GROUP9type=number&GROUP10fields=PRODUC T_GROUP&eqGROUP10data=400.1&GROUP10type=number&GROUP11fields=PRODUCT_GROUP&e qGROUP11data=400.5&GROUP11type=number&eqPROD_VISIBLEdatarq=T&nePRICEdatarq=[ BLANK]&nePROD_NAMEdatarq=[BLANK]&dePROD_SPECIALsort=1&allhit=1&asSKUsort=2&s tartat=1&max=250I going to have fun tonight .. I can tell ;) Alain> 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 ? > > ------------------------------------------------------------- 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:

    
  1. Re: URGENT: PERHAPS A BUG, woFIELDdata & FIELDword=ww (Andrew Simpson 2002)
  2. Re: URGENT: PERHAPS A BUG, woFIELDdata & FIELDword=ww (Alain Russell 2002)
That would be ok but the search string also contains a whole bunch of other conditions .. As you will see below:&eqPROD_VISIBLEdatarq=T&nePRICEdatarq=[BLANK]&nePROD_NAMEdatarq=[BLANK]&dePR OD_SPECIALsort=1&asSKUsort=2&allhit=1&startat=[startat]&max=[max_found_items ]So I need to be able to specify FIELDSdatarq on the group .. But then it won't work with more than one on the same field.Just for reference - this would be the entire search string .. db=/db/products.db&GROUP1fields=PRODUCT_GROUP&eqGROUP1data=400.7&GROUP1type= number&GROUP2fields=PRODUCT_GROUP&eqGROUP2data=400.9&GROUP2type=number&GROUP 3fields=PRODUCT_GROUP&eqGROUP3data=400.3&GROUP3type=number&GROUP4fields=PROD UCT_GROUP&eqGROUP4data=400.6&GROUP4type=number&GROUP5fields=PRODUCT_GROUP&eq GROUP5data=400.4&GROUP5type=number&GROUP6fields=PRODUCT_GROUP&eqGROUP6data=4 00.2&GROUP6type=number&GROUP7fields=PRODUCT_GROUP&eqGROUP7data=400.8&GROUP7t ype=number&GROUP8fields=PRODUCT_GROUP&eqGROUP8data=18&GROUP8type=number&GROU P9fields=PRODUCT_GROUP&eqGROUP9data=2&GROUP9type=number&GROUP10fields=PRODUC T_GROUP&eqGROUP10data=400.1&GROUP10type=number&GROUP11fields=PRODUCT_GROUP&e qGROUP11data=400.5&GROUP11type=number&eqPROD_VISIBLEdatarq=T&nePRICEdatarq=[ BLANK]&nePROD_NAMEdatarq=[BLANK]&dePROD_SPECIALsort=1&allhit=1&asSKUsort=2&s tartat=1&max=250I going to have fun tonight .. I can tell ;) Alain> 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 ? > > ------------------------------------------------------------- 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/ Alain Russell

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:

Help!!!! (1997) Active Server Code... (1998) MATH TIME (1997) PCS Frames (1997) assigning a id no. (2000) Kaaaaahhhhhhhnnnnnnn! (1997) [switch][case] (2004) New iMac, now ... how do I make webdna serve .html files? (2005) Plugin or CGI or both (1997) Automatic POST arg sending? (1998) how to post without certain data appearing in the html source (2001) HELP WITH DATES (1997) HELP WITH DATES (1997) thisurl & arguments (2000) Extended [ConvertChars] (1997) OT: Sending email to lots of subscribers (1999) [WebDNA] parsing xml (2010) WebCat and Phantom (2000) Great product and great job ! (1997) Storebuilder, Smith-Micro Tech Support (2000)