Re: [WebDNA] Searching Possible Bug

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 102976
interpreted = N
texte = I think you might want to try &AllHit=1 on the end of your search. From the docs... Note: fields are sorted within equally-ranked groups of found items, which means that all the "best match" records at the top of the list get sorted alphabetically, then the "next-best" records are sorted after that, and so on. Often, if it is important that records be sorted purely alphabetically (ignoring their 'rank'), you will need to put "AllHit=1" into your search criteria. Paul On 20 Jul 2009, at 12:08, Steve Craig wrote: > Hi > > Hopefully someone can help, To my way of thinking I may have found a > little bug, but it may not be, just never noticed this behaviour > before. > > I have a database full of news stories. The DB has a field called > HeadlinesSections which is a news category. An individual story > could be in multiple categories. I am doing a search for new stories > that are either in the Bioenergy or Microgeneration section. I want > the results listed by date order so my search is basically... > > [search db=My.db&woHeadlinesSectionsdatarq=Bioenergy > Microgeneration&deHeadlinesDatesort=1&HeadlinesDatetype=date] > > It works in as much as I get the correct records but because 3 of > the records are marked in both sections they always show at the top > of the list. It seems to override the date sort and treat the 3 > records as more relevant because they have both categories. (hope > that makes sense) > > Is this as expected? Does the wo search override sorts? Is there a > way round it without using tables? > > A sample page is at http://aese.asylumweb.net/ > Industry_headlines.html although I'm working on it so it may not be > there for ever. The top 3 records,.. > > Measures on renewable... > Best green power... > IFA is 8000.... > > are in both categories but should not be at the top as they are > older stories. > Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Searching Possible Bug (Donovan Brooke 2009)
  2. Re: [WebDNA] Searching Possible Bug (Govinda 2009)
  3. Re: [WebDNA] Searching Possible Bug (Frank Nordberg 2009)
  4. Re: [WebDNA] Searching Possible Bug (Donovan Brooke 2009)
  5. Re: [WebDNA] Searching Possible Bug (Frank Nordberg 2009)
  6. Re: [WebDNA] Searching Possible Bug (Donovan Brooke 2009)
  7. Re: [WebDNA] Searching Possible Bug (Donovan Brooke 2009)
  8. Re: [WebDNA] Searching Possible Bug (Steve Craig 2009)
  9. Re: [WebDNA] Searching Possible Bug ("Brian Harrington, Broker" 2009)
  10. Re: [WebDNA] Searching Possible Bug (Terry Wilson 2009)
  11. Re: [WebDNA] Searching Possible Bug (Terry Wilson 2009)
  12. Re: [WebDNA] Searching Possible Bug ("Brian Harrington, Broker" 2009)
  13. Re: [WebDNA] Searching Possible Bug (Donovan Brooke 2009)
  14. Re: [WebDNA] Searching Possible Bug ("Brian Harrington, Broker" 2009)
  15. Re: [WebDNA] Searching Possible Bug ("Brian Harrington, Broker" 2009)
  16. Re: [WebDNA] Searching Possible Bug ("Brian Harrington, Broker" 2009)
  17. Re: [WebDNA] Searching Possible Bug (Tom Duke 2009)
  18. Re: [WebDNA] Searching Possible Bug (Steve Craig 2009)
  19. Re: [WebDNA] Searching Possible Bug (Tom Duke 2009)
  20. Re: [WebDNA] Searching Possible Bug (Steve Craig 2009)
  21. Re: [WebDNA] Searching Possible Bug (Paul Willis 2009)
  22. [WebDNA] Searching Possible Bug (Steve Craig 2009)
I think you might want to try &AllHit=1 on the end of your search. From the docs... Note: fields are sorted within equally-ranked groups of found items, which means that all the "best match" records at the top of the list get sorted alphabetically, then the "next-best" records are sorted after that, and so on. Often, if it is important that records be sorted purely alphabetically (ignoring their 'rank'), you will need to put "AllHit=1" into your search criteria. Paul On 20 Jul 2009, at 12:08, Steve Craig wrote: > Hi > > Hopefully someone can help, To my way of thinking I may have found a > little bug, but it may not be, just never noticed this behaviour > before. > > I have a database full of news stories. The DB has a field called > HeadlinesSections which is a news category. An individual story > could be in multiple categories. I am doing a search for new stories > that are either in the Bioenergy or Microgeneration section. I want > the results listed by date order so my search is basically... > > [search db=My.db&woHeadlinesSectionsdatarq=Bioenergy > Microgeneration&deHeadlinesDatesort=1&HeadlinesDatetype=date] > > It works in as much as I get the correct records but because 3 of > the records are marked in both sections they always show at the top > of the list. It seems to override the date sort and treat the 3 > records as more relevant because they have both categories. (hope > that makes sense) > > Is this as expected? Does the wo search override sorts? Is there a > way round it without using tables? > > A sample page is at http://aese.asylumweb.net/ > Industry_headlines.html although I'm working on it so it may not be > there for ever. The top 3 records,.. > > Measures on renewable... > Best green power... > IFA is 8000.... > > are in both categories but should not be at the top as they are > older stories. > Paul Willis

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:

What's wrong with this [append] context? (2000) Generating Report Totals (1997) WC2b12: Yes, Formulas.db is for real (1997) Stumpted Again (1997) WebCatalog Features (1997) Listserver problem (1997) Quick Replace Question (2003) Resume Catalog ? (1997) Grep is Broke (2004) Ampersand (1997) MacWEEK article help needed (1996) Separate SSL Server (1997) javascript newPopwin and webcat (1998) read and write you own cookies with webcat (1997) Search/sort in URL Was: GuestBook example (1997) WCS Newbie question (1997) Resume Catalog ? (1997) WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997) Summing fields (1997) http upload (2001)