Re: URGENT: PERHAPS A BUG, woFIELDdata & FIELDword=ww
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 45686
interpreted = N
texte = So smithmicro doesn't care that this doesn't work as it should or am imissing something?Why is it that we have to build badly designed database schemas so we canwork with the poor searching methods.A nice addition to an upcoming version of webcat would be to allow us to useSQL syntax and methods to interact with webdna ram datbases... there arejust too many limitations with the current functionality.----- Original Message -----From: Alain Russell
To: WebCatalog Talk Sent: Friday, November 22, 2002 7:21 PMSubject: Re: URGENT: PERHAPS A BUG, woFIELDdata & FIELDword=ww> That would be ok but the search string also contains a whole bunch ofother> 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=250>> I going to have fun tonight .. I can tell ;)> Alain>> > I think the results you see are valid. If one of the words you'rematching 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, notnumbers.> > The wbrk parameter affects the search string - not the values in thedatabase> > field. You're correct that wo is not a valid comparison operator fornumeric> > fields. In this case you should do this (I haven't tested, so it mayneed> > 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 GROUPXparameters in> > a loop context.> >> > I hope this helps clear some things up and get's your signoff so you canget> > paid :>> >> > John.> >> >> I saw this in the archives a few days ago and now it has affected us ..> >> We have a search as follows> >>> >> [searchdb=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 2out> >> of the search string this works perfectly. We have tried all sorts ofother> >> 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/-------------------------------------------------------------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:
So smithmicro doesn't care that this doesn't work as it should or am imissing something?Why is it that we have to build badly designed database schemas so we canwork with the poor searching methods.A nice addition to an upcoming version of webcat would be to allow us to useSQL syntax and methods to interact with webdna ram datbases... there arejust too many limitations with the current functionality.----- Original Message -----From: Alain Russell To: WebCatalog Talk Sent: Friday, November 22, 2002 7:21 PMSubject: Re: URGENT: PERHAPS A BUG, woFIELDdata & FIELDword=ww> That would be ok but the search string also contains a whole bunch ofother> 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=250>> I going to have fun tonight .. I can tell ;)> Alain>> > I think the results you see are valid. If one of the words you'rematching 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, notnumbers.> > The wbrk parameter affects the search string - not the values in thedatabase> > field. You're correct that wo is not a valid comparison operator fornumeric> > fields. In this case you should do this (I haven't tested, so it mayneed> > 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 GROUPXparameters in> > a loop context.> >> > I hope this helps clear some things up and get's your signoff so you canget> > paid :>> >> > John.> >> >> I saw this in the archives a few days ago and now it has affected us ..> >> We have a search as follows> >>> >> [searchdb=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 2out> >> of the search string this works perfectly. We have tried all sorts ofother> >> 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/-------------------------------------------------------------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/
Andrew Simpson
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:
Running 2 two WebCatalog.acgi's (1996)
Security Question (1997)
Problems passing [SKU] with $Replace in 2.0 (1997)
sort problems....bug or brain fart? (1997)
Version f1 status (1997)
Explorer 3.0/ Access Denied! (1997)
show if date < expiry date (2002)
Re1000002: Setting up shop (1997)
Forms Search Questions (1997)
Download Question (1997)
Separate SSL Server (1997)
replace problem (1999)
More on the email templates (1997)
Fedora Core 3 and WebDNA (2005)
PIXO (1997)
suffix mapping for NT? (1997)
Format all of a sudden doesn't work (1997)
Calculating multiple shipping... (1997)
Use of Back and Reload Buttons on ShoppingCart page? (1997)
Multiple catalog databases and showcart (1997)