oddball sorting problem

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 55043
interpreted = N
texte = I have this: [search ....group1field=date1+date2&group1type=date&gegroup1datarq=[date]&date1type=date&date1sort=1] I originally had this: [search ...date1type=date&gedate1datarq=[date]&date1sort=1] The original search returned the records in the ascending order that I expected. When I altered it to include a second date (some events might have two dates), now it sorts screwy. Events with two dates float to the top (sorted correctly if both dates meet the ge criterion), followed by double dates where one date meets the requirement, and finally, the single date items (again, sorted correctly). What is causing the two-date items to precede the others? Maybe a clarification of what exactly is happening with grouped fields will help. I have it roughed out at http://terryfic.com/~yardsales/ Feel free to play with it. It will be up for a few more days as I develop it. Thanks, Terry ------------------------------------------------------------- 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:

    
  1. Re: oddball sorting problem ( Terry Wilson 2003)
  2. Re: oddball sorting problem [feature request] ( Donovan Brooke 2003)
  3. Re: oddball sorting problem ( Brian Fries 2003)
  4. Re: oddball sorting problem ( Terry Wilson 2003)
  5. Re: oddball sorting problem ( Donovan Brooke 2003)
  6. oddball sorting problem -- almost okay now ( Terry Wilson 2003)
  7. Re: oddball sorting problem ( Tim Robinson 2003)
  8. Re: oddball sorting problem ( "WebDna @" 2003)
  9. oddball sorting problem ( Terry Wilson 2003)
I have this: [search ....group1field=date1+date2&group1type=date&gegroup1datarq=[date]&date1type=date&date1sort=1] I originally had this: [search ...date1type=date&gedate1datarq=[date]&date1sort=1] The original search returned the records in the ascending order that I expected. When I altered it to include a second date (some events might have two dates), now it sorts screwy. Events with two dates float to the top (sorted correctly if both dates meet the ge criterion), followed by double dates where one date meets the requirement, and finally, the single date items (again, sorted correctly). What is causing the two-date items to precede the others? Maybe a clarification of what exactly is happening with grouped fields will help. I have it roughed out at http://terryfic.com/~yardsales/ Feel free to play with it. It will be up for a few more days as I develop it. Thanks, Terry ------------------------------------------------------------- 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/ 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:

Uh...can someone help me out with the b10? (1997) Email encryption (1998) File Uploads... (1997) docs for WebCatalog2 (1997) webcat license???? (1997) 3.08 has trouble keeping the serial # ?? (2000) Help with update to 2.11 (1998) Stop page auto. refreshing (2004) [WebDNA] read database from other domain (2015) [shownext] and sort (1998) More on the email templates (1997) Expert tech support -- a fast and simple solution (long) ... (2000) Sort Order on a page search (1997) Mystery File (2005) Get Cookie problem..... (2000) WCS Newbie question (1997) Memory Error message (1998) ShowNext (1997) RE: Ongoing group search problems ... (1997) WebCat virtual postcard is done! Thanks for the help! (1998)