Re: [WebDNA] Exclude found items in a 2nd search

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 112742
interpreted = N
texte = 325 Excellent! Glad you got it working. Terry On Tue, 26 Apr 2016 17:44:29 -0500 Richard Kwasniewski wrote: Thanks Terry. =20 All worked well after I added this to my 2nd search command =20 &wnSKUdatarq=3D[items]&SKUwbrk=3D[url],[/url] =20 The 6 randomly found SKUs in the 1st search were omitted in the results of that 2nd search..... =20 =20 =20 On Tue, Apr 26, 2016 at 11:41 AM, Terry Wilson wrote: =20 > Initialize your variable before the founditems loop=20 >([text]items=3D[/text]), > then in your founditems loop, add them to the same text variable. > > [text]items=3D[items],[sku][/text] > > Since you're on the same page, it's easy; [items] can be used to=20 >exclude > them in the next search. > > On Tue, 26 Apr 2016 11:03:52 -0500 > > Richard Kwasniewski wrote: > But since I'm showing 6 random items found initially, I can't seem=20 >to > grab > these 6 SKUs and place them anywhere, just one. > Adding [text show=3DT]found=3D[SKU][/text] just shows me the last SKU= =20 >of > the 6, > not the other 5. > I'd need the other 5 snatched up somehow > Also wouldn't hidden input fields be used only if I was passing=20 >info > to > another page? I'm not, all this is taking place on the same page at > the > same time. > On Tue, Apr 26, 2016 at 10:56 AM, Terry Wilson=20 > > wrote: > > >> Because your sort is random. No two searches will be the same. It=20 >>seemed >> to work the first time because it just didn't happen to find any of=20 >>the >> previous ones. Please see my previous post and the followup by=20 >>Lawrence. >> >> Terry >> >> >> On Tue, 26 Apr 2016 10:31:41 -0500 >> Richard Kwasniewski wrote: >> Not sure what happened, it seemed like adding the "startat=3D7" did >> work >> initially, but no more.... I may have missed matching up the items. >> here is my search code.: >> [search >> >> >> db=3D^/rs/products.db&woSECTIONSdatarq=3D12&SECTIONSword=3Dww&namewbr= k=3D+&eqVisibledatarq=3DT&eqFeatureddatarq=3DYes&TITLEsort=3D1&TITLEsdir=3D= ra&max=3D6] >> [founditems] >> 6 random items shown..... >> [/founditems] >> [/search] >> Right beneath this I would have my 2nd search: >> [search >> >> >> db=3D^/rs/products.db&woSECTIONSdatarq=3D12&SECTIONSword=3Dww&namewbr= k=3D+&eqVisibledatarq=3DT&eqFeatureddatarq=3DYes&TITLEsort=3D1&TITLEsdir=3D= ra] >> [founditems] >> Show all other items omitting the 6 found above.... >> [/founditems] >> [/search] >> All this takes place on the exact same page, so cookies don't seem=20 >>to >> be an >> option.... >> Trying the text variable route.... if I add this within the 1st >> search >> [text show=3DT]found=3D[SKU][/text] >> shows me the SKUs of the 6 chosen randomly in that 1st search, but >> how >> would I place all 6 of those SKUs within that 2nd search? >> &neSKUdatarq=3D[found] is what I was thinking, but that can't work o= n=20 >>6 >> SKUs >> On Tue, Apr 26, 2016 at 8:09 AM, Lawrence Banahan >> >> wrote: >> >> >> Hi, you could also use a hidden input to keep the previous IDs and=20 >>exclude >>> them from next search >>> Lawrence >>> >>> 2016-04-26 14:57 GMT+02:00 Terry Wilson : >>> >>> But you said you were searching for random results. I don't see how=20 >>>this >>> >>>> would work. >>>> >>>> You could collect the record IDs from the first search in a cookie,=20 >>>>and >>>> exclude those from the second search, or if on the same page, collec= t >>>> them >>>> in a text variable. >>>> >>>> Terry >>>> >>>> Sent from my iPad >>>> >>>> On Apr 26, 2016, at 5:17 AM, Richard Kwasniewski=20 >>>> >>>> wrote: >>>> >>>> Well all righty... >>>> >>>> That "startat=3D7" seems to work just fine with that 2nd search/resu= lts >>>> etc. >>>> >>>> Thanks >>>> >>>> >>>> On Tue, Apr 26, 2016 at 6:53 AM, Tom Duke >>>> wrote: >>>> >>>> Richard, >>>> >>>>> >>>>> Hi - if you have the same search and sorting criteria, then add: >>>>> >>>>> &startat=3D7 >>>>> >>>>> to your second search. >>>>> >>>>> - Tom >>>>> >>>>> >>>>> >>>>> --------------------------------------------------------- This=20 >>>>>message >>>>> is sent to you because you are subscribed to the mailing list . To >>>>> unsubscribe, E-mail to: archives: >>>>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>>>> support@webdna.us >>>>> >>>>> >>>> >>>> --------------------------------------------------------- This=20 >>>>message >>>> is >>>> sent to you because you are subscribed to the mailing list . To >>>> unsubscribe, E-mail to: archives: >>>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>>> support@webdna.us >>>> >>>> --------------------------------------------------------- This=20 >>>>message >>>> is >>>> sent to you because you are subscribed to the mailing list . To >>>> unsubscribe, E-mail to: archives: >>>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>>> support@webdna.us >>>> >>>> >>>> --------------------------------------------------------- This=20 >>>>message >>> is >>> sent to you because you are subscribed to the mailing list . To >>> unsubscribe, E-mail to: archives: >>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>> support@webdna.us >>> >>> --------------------------------------------------------- >>> >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >> >> --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Exclude found items in a 2nd search ("Terry Wilson" 2016)
  2. Re: [WebDNA] Exclude found items in a 2nd search (Richard Kwasniewski 2016)
  3. Re: [WebDNA] Exclude found items in a 2nd search ("Terry Wilson" 2016)
  4. Re: [WebDNA] Exclude found items in a 2nd search (Richard Kwasniewski 2016)
  5. Re: [WebDNA] Exclude found items in a 2nd search ("Terry Wilson" 2016)
  6. Re: [WebDNA] Exclude found items in a 2nd search (Richard Kwasniewski 2016)
  7. Re: [WebDNA] Exclude found items in a 2nd search (Lawrence Banahan 2016)
  8. Re: [WebDNA] Exclude found items in a 2nd search (Terry Wilson 2016)
  9. Re: [WebDNA] Exclude found items in a 2nd search (Richard Kwasniewski 2016)
  10. Re: [WebDNA] Exclude found items in a 2nd search (Tom Duke 2016)
  11. [WebDNA] Exclude found items in a 2nd search (Richard Kwasniewski 2016)
325 Excellent! Glad you got it working. Terry On Tue, 26 Apr 2016 17:44:29 -0500 Richard Kwasniewski wrote: Thanks Terry. =20 All worked well after I added this to my 2nd search command =20 &wnSKUdatarq=3D[items]&SKUwbrk=3D[url],[/url] =20 The 6 randomly found SKUs in the 1st search were omitted in the results of that 2nd search..... =20 =20 =20 On Tue, Apr 26, 2016 at 11:41 AM, Terry Wilson wrote: =20 > Initialize your variable before the founditems loop=20 >([text]items=3D[/text]), > then in your founditems loop, add them to the same text variable. > > [text]items=3D[items],[sku][/text] > > Since you're on the same page, it's easy; [items] can be used to=20 >exclude > them in the next search. > > On Tue, 26 Apr 2016 11:03:52 -0500 > > Richard Kwasniewski wrote: > But since I'm showing 6 random items found initially, I can't seem=20 >to > grab > these 6 SKUs and place them anywhere, just one. > Adding [text show=3DT]found=3D[SKU][/text] just shows me the last SKU= =20 >of > the 6, > not the other 5. > I'd need the other 5 snatched up somehow > Also wouldn't hidden input fields be used only if I was passing=20 >info > to > another page? I'm not, all this is taking place on the same page at > the > same time. > On Tue, Apr 26, 2016 at 10:56 AM, Terry Wilson=20 > > wrote: > > >> Because your sort is random. No two searches will be the same. It=20 >>seemed >> to work the first time because it just didn't happen to find any of=20 >>the >> previous ones. Please see my previous post and the followup by=20 >>Lawrence. >> >> Terry >> >> >> On Tue, 26 Apr 2016 10:31:41 -0500 >> Richard Kwasniewski wrote: >> Not sure what happened, it seemed like adding the "startat=3D7" did >> work >> initially, but no more.... I may have missed matching up the items. >> here is my search code.: >> [search >> >> >> db=3D^/rs/products.db&woSECTIONSdatarq=3D12&SECTIONSword=3Dww&namewbr= k=3D+&eqVisibledatarq=3DT&eqFeatureddatarq=3DYes&TITLEsort=3D1&TITLEsdir=3D= ra&max=3D6] >> [founditems] >> 6 random items shown..... >> [/founditems] >> [/search] >> Right beneath this I would have my 2nd search: >> [search >> >> >> db=3D^/rs/products.db&woSECTIONSdatarq=3D12&SECTIONSword=3Dww&namewbr= k=3D+&eqVisibledatarq=3DT&eqFeatureddatarq=3DYes&TITLEsort=3D1&TITLEsdir=3D= ra] >> [founditems] >> Show all other items omitting the 6 found above.... >> [/founditems] >> [/search] >> All this takes place on the exact same page, so cookies don't seem=20 >>to >> be an >> option.... >> Trying the text variable route.... if I add this within the 1st >> search >> [text show=3DT]found=3D[SKU][/text] >> shows me the SKUs of the 6 chosen randomly in that 1st search, but >> how >> would I place all 6 of those SKUs within that 2nd search? >> &neSKUdatarq=3D[found] is what I was thinking, but that can't work o= n=20 >>6 >> SKUs >> On Tue, Apr 26, 2016 at 8:09 AM, Lawrence Banahan >> >> wrote: >> >> >> Hi, you could also use a hidden input to keep the previous IDs and=20 >>exclude >>> them from next search >>> Lawrence >>> >>> 2016-04-26 14:57 GMT+02:00 Terry Wilson : >>> >>> But you said you were searching for random results. I don't see how=20 >>>this >>> >>>> would work. >>>> >>>> You could collect the record IDs from the first search in a cookie,=20 >>>>and >>>> exclude those from the second search, or if on the same page, collec= t >>>> them >>>> in a text variable. >>>> >>>> Terry >>>> >>>> Sent from my iPad >>>> >>>> On Apr 26, 2016, at 5:17 AM, Richard Kwasniewski=20 >>>> >>>> wrote: >>>> >>>> Well all righty... >>>> >>>> That "startat=3D7" seems to work just fine with that 2nd search/resu= lts >>>> etc. >>>> >>>> Thanks >>>> >>>> >>>> On Tue, Apr 26, 2016 at 6:53 AM, Tom Duke >>>> wrote: >>>> >>>> Richard, >>>> >>>>> >>>>> Hi - if you have the same search and sorting criteria, then add: >>>>> >>>>> &startat=3D7 >>>>> >>>>> to your second search. >>>>> >>>>> - Tom >>>>> >>>>> >>>>> >>>>> --------------------------------------------------------- This=20 >>>>>message >>>>> is sent to you because you are subscribed to the mailing list . To >>>>> unsubscribe, E-mail to: archives: >>>>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>>>> support@webdna.us >>>>> >>>>> >>>> >>>> --------------------------------------------------------- This=20 >>>>message >>>> is >>>> sent to you because you are subscribed to the mailing list . To >>>> unsubscribe, E-mail to: archives: >>>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>>> support@webdna.us >>>> >>>> --------------------------------------------------------- This=20 >>>>message >>>> is >>>> sent to you because you are subscribed to the mailing list . To >>>> unsubscribe, E-mail to: archives: >>>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>>> support@webdna.us >>>> >>>> >>>> --------------------------------------------------------- This=20 >>>>message >>> is >>> sent to you because you are subscribed to the mailing list . To >>> unsubscribe, E-mail to: archives: >>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>> support@webdna.us >>> >>> --------------------------------------------------------- >>> >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >> >> --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . "Terry Wilson"

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:

Sku numbers (1997) Separate SSL Server (1997) decrypt problem (2004) Wierd thing in ViewOrder.tpl (1999) Okay, I give up... (1999) WebCatalog Upgrade Pricing? (1997) [OT] was SQL Query Question (2001) OT - asp snippet similar to [!][/!] (2003) Password Group (2002) WebCat and WebTV (1997) Silly Question (1997) WebCat2 - Getting to the browser's username/password data (1997) writing orders to a db (1997) catching WebDNA error messages (2003) syntax question, not in online refernce (1997) Formula (2004) [username][password] not showing up. (2000) Webcat vs Tango (2000) still having shipCost.db Problem (1997) WebCat2b13MacPlugIn - [showif][search][/showif] (1997)