oddball sorting problem -- almost okay now

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 55046
interpreted = N
texte = Doing a little more digging, I found allhit=1 in the online docs to turn off relevancy, and that cleared it up, mostly.However, when the second date is still in the future, it is sorting on the 1st (past) date. I'd rather have the 2nd date be the one in the sort order. I don't see a straightforward solution to this without using a trigger to update the database daily, or something, so I guess I'll just live with it.TerryAt 11:22 PM -0500 12/17/03, Terry Wilson wrote: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:

oddball sorting problem -- almost okay now ( Terry Wilson 2003)

Doing a little more digging, I found allhit=1 in the online docs to turn off relevancy, and that cleared it up, mostly.However, when the second date is still in the future, it is sorting on the 1st (past) date. I'd rather have the 2nd date be the one in the sort order. I don't see a straightforward solution to this without using a trigger to update the database daily, or something, so I guess I'll just live with it.TerryAt 11:22 PM -0500 12/17/03, Terry Wilson wrote: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!

oddball sorting problem -- almost okay now

2003

Top Articles:

Related Readings: