Re: Need help!! on searching in two databases.

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19639
interpreted = N
texte = >>I want to find all records matching an id number in the first table, the >>sort all the found records _alphabetically_ based on the name related to >>the id number in the second table. By doing it the way it is described in >>the link above, I am not able to do so. The order is determined in the >>first search. > >I must not understand what you're trying to do. What's wrong with telling >the interior [search] to sort? >Well, it might be me that doesnt understand the document you pointed to. Ill try to explain.The way it is done in the document you pointed to, is that the exterior search gets all the numbers, then search them up one by one in a second database within the [founditems] context. As the second database in my case contains only unique id numbers, the interior search will return only one record per number, always. And that is not much to sort.What I am trying to do, is to take the list of unique ids, search for them in a second database and return the matching records ( only one record for each id number) in a sorted manner. This works as long as the exterior search return less than 50 records. When the exterior search returns more than 50 records (I do not know the excact number), the interior search returns more/less records than it should be. That this ia a misbehaviour, is apparent because the search first returns the right records sorted a-z, the returns some more records, starting at 'a' again.>>This DOES work when the search doesnt >>return to many records, and its pretty fast to, but when the first search >>returns about 50 records or more, the second search returns more records >>than the first. And this should surely not be so. Is there a way around >>this, or is this a misbehaveour of webcatalog? > >Probably it is accidentally finding substrings of text that *happen* to >match. Try adding WORD=ww to force only Whole Word matches.My id numbers are all equally long and unique, thus any substring match is out of the question. I tried with the WORD=ww, with no difference.> >Technical Support | ==== eCommerce and Beyond ==== >Pacific Coast Software | WebCatalog, WebMerchant, >11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, >San Diego, CA 92128 | Typhoon >619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Need help!! on searching in two databases. (Per Christian Lied 1998)
  2. Re: Need help!! on searching in two databases. (PCS Technical Support 1998)
  3. Re: Need help!! on searching in two databases. (Per Christian Lied 1998)
  4. Re: Need help!! on searching in two databases. (PCS Technical Support 1998)
  5. Need help!! on searching in two databases. (Per Christian Lied 1998)
>>I want to find all records matching an id number in the first table, the >>sort all the found records _alphabetically_ based on the name related to >>the id number in the second table. By doing it the way it is described in >>the link above, I am not able to do so. The order is determined in the >>first search. > >I must not understand what you're trying to do. What's wrong with telling >the interior [search] to sort? >Well, it might be me that doesnt understand the document you pointed to. Ill try to explain.The way it is done in the document you pointed to, is that the exterior search gets all the numbers, then search them up one by one in a second database within the [founditems] context. As the second database in my case contains only unique id numbers, the interior search will return only one record per number, always. And that is not much to sort.What I am trying to do, is to take the list of unique ids, search for them in a second database and return the matching records ( only one record for each id number) in a sorted manner. This works as long as the exterior search return less than 50 records. When the exterior search returns more than 50 records (I do not know the excact number), the interior search returns more/less records than it should be. That this ia a misbehaviour, is apparent because the search first returns the right records sorted a-z, the returns some more records, starting at 'a' again.>>This DOES work when the search doesnt >>return to many records, and its pretty fast to, but when the first search >>returns about 50 records or more, the second search returns more records >>than the first. And this should surely not be so. Is there a way around >>this, or is this a misbehaveour of webcatalog? > >Probably it is accidentally finding substrings of text that *happen* to >match. Try adding WORD=ww to force only Whole Word matches.My id numbers are all equally long and unique, thus any substring match is out of the question. I tried with the WORD=ww, with no difference.> >Technical Support | ==== eCommerce and Beyond ==== >Pacific Coast Software | WebCatalog, WebMerchant, >11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, >San Diego, CA 92128 | Typhoon >619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Per Christian Lied

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:

[addlineitems] display (1997) Searching multiple databases (1998) Faxing orders in place of email (1997) RE: E-mailer error codes (1997) RE: File Uploads (1998) Searching multiple fields (1997) AUTONUMBER (2003) Database Upload (2000) Odd (2001) two unique banners on one page (1997) OSX Applescripts -- Anyone? please? (2004) nested context (1998) Web Developer Product Awards (1997) Mystery authentication (1997) WebCat2 beta 11 - new prefs ... (1997) [OT] SMTP gateway software for Mac (1999) Question about links (1999) Using Plug-In while running 1.6.1 (1997) WebCommerce: Folder organization ? (1997) macosx 1 process, linux N processes, macosx chokes under load (2001)