Re: Sorting when searching with grouped fields
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43406
interpreted = N
texte = Ah... Add &allhit=T to your search so that WebDNA will ignore it's internal ranking when sorting.- brianAt 5:28 PM -0600 9/13/02, Myron Hintz wrote: >Brian, > >The 6th to the 7th row of the results jumps from 731463 to 731471. > >Myron > >> The type is a good thing to add, though it should be num not >> number. (maybe number works? I've never tried it, but it's not >> documented that way.) >> >> But, I don't expect this will make any difference in this case, as >> all values shown (days since 0/0/00) will sort the same as text (at >> least for the next 624 years). >> >> But I don't see anything wrong with the sort order in the sample >> results - the PROPOSAL_DATE is sorted descending, as specified in the >> search. >> >> What is the problem? >> >> - brian >> >> >> At 10:41 AM 9/14/02, Alain Russell wrote: >>> You need to define the field for the sort .. >>> >>> &PROPOSAL_DATEtype=number >>> >>> Alain >>> >>>> I am trying to build a search which will find all records where >>>>the fields >>>> PROPOSAL_DATE or UPDATED fall in a range and then sort the results by >>>> PROPOSAL_DATE. The search string below finds all the correct records but >>>> they are sorted incorrectly: >>>> >>>> >>>> >>>>SEARCH_STRING:db=proposal.db&eqSTATUSdatarq=ACTIVE&GROUP1field=UPDATED+PROPO >>>> SAL_DATE&rnGROUP1datarq=731457 731471&dePROPOSAL_DATEsort=1 >>>> >>>> Results: >>>> PROPOSAL_DATE UPDATED >>>> 731471 731471 >>>> 731471 731471 >>>> 731470 731471 >>>> 731468 731469 >>>> 731465 731468 >>>> 731463 731464 >>>> 731471 >>>> 731467 >>>> 731463 >>>> 731463 >>>> 731463 >>>> 731462 >>>> 731462 >>>> 731457 >>>> 731457 >>>> 731457 >>>> 731454 731461 >>>> 731399 731462 >>>> 731218 731469 >>>> >>>> How can I build the search to get the results I want? >>>> >>>> Myron Hintz >>>> WebCatalog Plug in 3.0.8/MAC OS 9 >>>> >>>> > > >------------------------------------------------------------- >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://search.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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Ah... Add &allhit=T to your search so that WebDNA will ignore it's internal ranking when sorting.- brianAt 5:28 PM -0600 9/13/02, Myron Hintz wrote: >Brian, > >The 6th to the 7th row of the results jumps from 731463 to 731471. > >Myron > >> The type is a good thing to add, though it should be num not >> number. (maybe number works? I've never tried it, but it's not >> documented that way.) >> >> But, I don't expect this will make any difference in this case, as >> all values shown (days since 0/0/00) will sort the same as text (at >> least for the next 624 years). >> >> But I don't see anything wrong with the sort order in the sample >> results - the PROPOSAL_DATE is sorted descending, as specified in the >> search. >> >> What is the problem? >> >> - brian >> >> >> At 10:41 AM 9/14/02, Alain Russell wrote: >>> You need to define the field for the sort .. >>> >>> &PROPOSAL_DATEtype=number >>> >>> Alain >>> >>>> I am trying to build a search which will find all records where >>>>the fields >>>> PROPOSAL_DATE or UPDATED fall in a range and then sort the results by >>>> PROPOSAL_DATE. The search string below finds all the correct records but >>>> they are sorted incorrectly: >>>> >>>> >>>> >>>>SEARCH_STRING:db=proposal.db&eqSTATUSdatarq=ACTIVE&GROUP1field=UPDATED+PROPO >>>> SAL_DATE&rnGROUP1datarq=731457 731471&dePROPOSAL_DATEsort=1 >>>> >>>> Results: >>>> PROPOSAL_DATE UPDATED >>>> 731471 731471 >>>> 731471 731471 >>>> 731470 731471 >>>> 731468 731469 >>>> 731465 731468 >>>> 731463 731464 >>>> 731471 >>>> 731467 >>>> 731463 >>>> 731463 >>>> 731463 >>>> 731462 >>>> 731462 >>>> 731457 >>>> 731457 >>>> 731457 >>>> 731454 731461 >>>> 731399 731462 >>>> 731218 731469 >>>> >>>> How can I build the search to get the results I want? >>>> >>>> Myron Hintz >>>> WebCatalog Plug in 3.0.8/MAC OS 9 >>>> >>>> > > >------------------------------------------------------------- >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://search.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://search.smithmicro.com/
Brian Fries
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:
Is there a way to just get to the last record in the database? (1997)
Problems with cybercash (2000)
OT: advice on Wintel server options (1998)
Three new problems ... (1997)
[ShowNext] (1997)
Forbidden CGI Error (1997)
[random] only for 1-100??? (1997)
RE: setting cookies then redirecting? (1998)
Auto-closing of databases (was DON'T use old cart file!) (1997)
Not really WebCat (1997)
Add message to Order (1997)
Prices Dropped (1998)
Part 2 - [showif] if variable exists (1998)
Major bug report on rootbeer (1997)
Help! WebCat2 bug (1997)
WebStar5 and realm authentication (2003)
Summary search -- speed (1997)
WebCatalog for Postcards ? (1997)
Null Chars (1999)
RE: Can a database get stomped by simultaneous access? (1997)