Re: [WebDNA] sort parameters in search
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 111861
interpreted = N
texte = Terry, thanks for putting this up.. always helps to understand. My .02=A2: "Repeated field on 1st & 2nd sort (FAIL)=94 I don=92t consider this a FAIL, but rather bad syntax. This goes for all = the =93Repeated=94 field tests. =93missing sort=3D2 (FAIL):=94 I think improvements could be made here, if indeed these are the results = for =93&lastsort=3D1&firstsort=3D3=94.=20 The Sort param should be a numerical ranking, where it doesn=92t matter = if an integer is missing.. and yes I agree, it should allow decimals. This would be a good refinement to me.=20 "bogus placeholder for sort=3D1 (FAIL):=94 Again, seems like bad syntax to me. Sincerely, Donovan On Jan 12, 2015, at 6:23 PM, Terry Wilson
wrote: > For those of you interested in the ramifications of deviating from the = prescribed sorting parameters in a search (or making typos), I made up a = little page to show what happens: >=20 > http://terryfic.com/webdna/sort.html >=20 >=20 > On Jan 12, 2015, at 8:59 AM, Terry Wilson wrote: >=20 >> Thanks Donovan. As often happens when I go to ask a question, in = documenting the problem, I often discover the answer myself. In this = case, when I made my first reply to you, it dawned on me that this is = would not merely be a tweak, but an entirely different way of managing = the sort. So if it's not easy, maybe it's better that the WSC resources = be put to other uses like fixing the IPaddress format. >>=20 >> But nevertheless, later today after I do my swim at the Y then take = my mother to lunch with some little old ladies, I'll throw together a = sample page. >>=20 >> I like the dialog going on right now for feature requests and = enhancements. >>=20 >> Sent from my iPad >>=20 >>> On Jan 12, 2015, at 8:35 AM, Donovan Brooke wrote: >>>=20 >>> Off the top of my head, sorting =93childs=94 are supposed to apply = to sorted parent ranks.. meaning sort2 works on the ranked match set of = sort1.=20 >>>=20 >>> So.. if there is no sort1 ranked set=85 There could be a subtle = issue on what you describe, but I don=92t have the time to test right = now. The reason I am asking for a reproducible test set is that I = personally value your opinion and when you suggest something, I = personally listen. But I wouldn=92t want WSC to mess with Search unless = there is a clear understanding of the issue and the fix.=20 >>>=20 >>> Note, I=92m not working with WSC at this point, so I have no say = other than a being a passionate end-user of the language.=20 >>>=20 >>> Sincerely, >>> Donovan >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> On Jan 12, 2015, at 10:16 AM, Terry Wilson = wrote: >>>>=20 >>>> Also, it was a feature request, not a request to help with a = workaround. I already do that. Thanks though! >>>>=20 >>>> Sent from my iPad >>>>=20 >>>>> On Jan 12, 2015, at 7:57 AM, Donovan Brooke = wrote: >>>>>=20 >>>>> Terry, I don=92t personally have much time these days to write out = my own test code for other peoples issues. >>>>>=20 >>>>> However, I am trying to help. Maybe someone else can test this. >>>>>=20 >>>>> Sincerely, >>>>> Donovan >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>>> On Jan 12, 2015, at 9:55 AM, Terry Wilson = wrote: >>>>>>=20 >>>>>> My guess is that sort1 is looked for, and if not found, no = further sorting is investigated. Likewise when there's no sort2, etc. = You can easily try this out on one of your own searches. >>>>>>=20 >>>>>> Sent from my iPad >>>>>>=20 >>>>>>> On Jan 12, 2015, at 7:12 AM, Donovan Brooke = wrote: >>>>>>>=20 >>>>>>> Hi Terry, >>>>>>>=20 >>>>>>> Are you saying later sort params get ignored if prior sort = params don=92t apply? >>>>>>>=20 >>>>>>> Can you post a test template and your desired results? >>>>>>>=20 >>>>>>> Donovan >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>> On Jan 11, 2015, at 11:06 PM, Terry Wilson = wrote: >>>>>>>>=20 >>>>>>>> I'd really to see the sort parameters in [search] sort = regardless of the specified number. How do I explain this. >>>>>>>>=20 >>>>>>>> &fieldAsort=3D1&fieldBsort=3D2&fieldCsort=3D3&fieldDsort=3D4 >>>>>>>>=20 >>>>>>>> But I only need fieldA to lead the sort for one condition. So = unless that comes up, I just hide fieldAsort=3D1 like so: >>>>>>>>=20 >>>>>>>> [showif = [specialcase]=3Dt]&fieldAsort=3D1[/showif]&fieldBsort=3D2&fieldCsort=3D3&f= ieldDsort=3D4 >>>>>>>>=20 >>>>>>>> This comes up from time to time, and actually right now it's = coming up for me again and as usual, I have to showif/hideif the entire = sort string for each condition instead of just slipping in the one that = I need for certain cases. >>>>>>>>=20 >>>>>>>> [showif = [specialcase]=3Dt]&fieldAsort=3D1&fieldBsort=3D2&fieldCsort=3D3&fieldDsort= =3D4[/showif] >>>>>>>> [hideif = [specialcase]=3Dt]&fieldBsort=3D1&fieldCsort=3D2&fieldDsort=3D3[/hideif] >>>>>>>>=20 >>>>>>>> kind of a pain in the ass when you're still deciding what to = best sort on - now you have 2 places to futz with as you refine. >>>>>>>>=20 >>>>>>>> Bonus points to also let those numbers be decimal. Let's say = sometimes you need an additional sort in the middle. Throw a showif on = fieldZsort=3D2.5 as needed: >>>>>>>>=20 >>>>>>>> = &fieldAsort=3D1&fieldBsort=3D2&fieldZsort=3D2.5&fieldCsort=3D3&fieldDsort=3D= 4--------------------------------------------------------- >>>>>>>> This message is sent to you because you are subscribed to >>>>>>>> the mailing list . >>>>>>>> To unsubscribe, E-mail to: >>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>> Bug Reporting: support@webdna.us >>>>>>>=20 >>>>>>> --------------------------------------------------------- >>>>>>> This message is sent to you because you are subscribed to >>>>>>> the mailing list . >>>>>>> To unsubscribe, E-mail to: >>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>> Bug Reporting: support@webdna.us >>>>>> --------------------------------------------------------- >>>>>> This message is sent to you because you are subscribed to >>>>>> the mailing list . >>>>>> To unsubscribe, E-mail to: >>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>> Bug Reporting: support@webdna.us >>>>>=20 >>>>> --------------------------------------------------------- >>>>> This message is sent to you because you are subscribed to >>>>> the mailing list . >>>>> To unsubscribe, E-mail to: >>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>> Bug Reporting: support@webdna.us >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Terry, thanks for putting this up.. always helps to understand. My .02=A2: "Repeated field on 1st & 2nd sort (FAIL)=94 I don=92t consider this a FAIL, but rather bad syntax. This goes for all = the =93Repeated=94 field tests. =93missing sort=3D2 (FAIL):=94 I think improvements could be made here, if indeed these are the results = for =93&lastsort=3D1&firstsort=3D3=94.=20 The Sort param should be a numerical ranking, where it doesn=92t matter = if an integer is missing.. and yes I agree, it should allow decimals. This would be a good refinement to me.=20 "bogus placeholder for sort=3D1 (FAIL):=94 Again, seems like bad syntax to me. Sincerely, Donovan On Jan 12, 2015, at 6:23 PM, Terry Wilson wrote: > For those of you interested in the ramifications of deviating from the = prescribed sorting parameters in a search (or making typos), I made up a = little page to show what happens: >=20 > http://terryfic.com/webdna/sort.html >=20 >=20 > On Jan 12, 2015, at 8:59 AM, Terry Wilson wrote: >=20 >> Thanks Donovan. As often happens when I go to ask a question, in = documenting the problem, I often discover the answer myself. In this = case, when I made my first reply to you, it dawned on me that this is = would not merely be a tweak, but an entirely different way of managing = the sort. So if it's not easy, maybe it's better that the WSC resources = be put to other uses like fixing the IPaddress format. >>=20 >> But nevertheless, later today after I do my swim at the Y then take = my mother to lunch with some little old ladies, I'll throw together a = sample page. >>=20 >> I like the dialog going on right now for feature requests and = enhancements. >>=20 >> Sent from my iPad >>=20 >>> On Jan 12, 2015, at 8:35 AM, Donovan Brooke wrote: >>>=20 >>> Off the top of my head, sorting =93childs=94 are supposed to apply = to sorted parent ranks.. meaning sort2 works on the ranked match set of = sort1.=20 >>>=20 >>> So.. if there is no sort1 ranked set=85 There could be a subtle = issue on what you describe, but I don=92t have the time to test right = now. The reason I am asking for a reproducible test set is that I = personally value your opinion and when you suggest something, I = personally listen. But I wouldn=92t want WSC to mess with Search unless = there is a clear understanding of the issue and the fix.=20 >>>=20 >>> Note, I=92m not working with WSC at this point, so I have no say = other than a being a passionate end-user of the language.=20 >>>=20 >>> Sincerely, >>> Donovan >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> On Jan 12, 2015, at 10:16 AM, Terry Wilson = wrote: >>>>=20 >>>> Also, it was a feature request, not a request to help with a = workaround. I already do that. Thanks though! >>>>=20 >>>> Sent from my iPad >>>>=20 >>>>> On Jan 12, 2015, at 7:57 AM, Donovan Brooke = wrote: >>>>>=20 >>>>> Terry, I don=92t personally have much time these days to write out = my own test code for other peoples issues. >>>>>=20 >>>>> However, I am trying to help. Maybe someone else can test this. >>>>>=20 >>>>> Sincerely, >>>>> Donovan >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>>> On Jan 12, 2015, at 9:55 AM, Terry Wilson = wrote: >>>>>>=20 >>>>>> My guess is that sort1 is looked for, and if not found, no = further sorting is investigated. Likewise when there's no sort2, etc. = You can easily try this out on one of your own searches. >>>>>>=20 >>>>>> Sent from my iPad >>>>>>=20 >>>>>>> On Jan 12, 2015, at 7:12 AM, Donovan Brooke = wrote: >>>>>>>=20 >>>>>>> Hi Terry, >>>>>>>=20 >>>>>>> Are you saying later sort params get ignored if prior sort = params don=92t apply? >>>>>>>=20 >>>>>>> Can you post a test template and your desired results? >>>>>>>=20 >>>>>>> Donovan >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>> On Jan 11, 2015, at 11:06 PM, Terry Wilson = wrote: >>>>>>>>=20 >>>>>>>> I'd really to see the sort parameters in [search] sort = regardless of the specified number. How do I explain this. >>>>>>>>=20 >>>>>>>> &fieldAsort=3D1&fieldBsort=3D2&fieldCsort=3D3&fieldDsort=3D4 >>>>>>>>=20 >>>>>>>> But I only need fieldA to lead the sort for one condition. So = unless that comes up, I just hide fieldAsort=3D1 like so: >>>>>>>>=20 >>>>>>>> [showif = [specialcase]=3Dt]&fieldAsort=3D1[/showif]&fieldBsort=3D2&fieldCsort=3D3&f= ieldDsort=3D4 >>>>>>>>=20 >>>>>>>> This comes up from time to time, and actually right now it's = coming up for me again and as usual, I have to showif/hideif the entire = sort string for each condition instead of just slipping in the one that = I need for certain cases. >>>>>>>>=20 >>>>>>>> [showif = [specialcase]=3Dt]&fieldAsort=3D1&fieldBsort=3D2&fieldCsort=3D3&fieldDsort= =3D4[/showif] >>>>>>>> [hideif = [specialcase]=3Dt]&fieldBsort=3D1&fieldCsort=3D2&fieldDsort=3D3[/hideif] >>>>>>>>=20 >>>>>>>> kind of a pain in the ass when you're still deciding what to = best sort on - now you have 2 places to futz with as you refine. >>>>>>>>=20 >>>>>>>> Bonus points to also let those numbers be decimal. Let's say = sometimes you need an additional sort in the middle. Throw a showif on = fieldZsort=3D2.5 as needed: >>>>>>>>=20 >>>>>>>> = &fieldAsort=3D1&fieldBsort=3D2&fieldZsort=3D2.5&fieldCsort=3D3&fieldDsort=3D= 4--------------------------------------------------------- >>>>>>>> This message is sent to you because you are subscribed to >>>>>>>> the mailing list . >>>>>>>> To unsubscribe, E-mail to: >>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>> Bug Reporting: support@webdna.us >>>>>>>=20 >>>>>>> --------------------------------------------------------- >>>>>>> This message is sent to you because you are subscribed to >>>>>>> the mailing list . >>>>>>> To unsubscribe, E-mail to: >>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>> Bug Reporting: support@webdna.us >>>>>> --------------------------------------------------------- >>>>>> This message is sent to you because you are subscribed to >>>>>> the mailing list . >>>>>> To unsubscribe, E-mail to: >>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>> Bug Reporting: support@webdna.us >>>>>=20 >>>>> --------------------------------------------------------- >>>>> This message is sent to you because you are subscribed to >>>>> the mailing list . >>>>> To unsubscribe, E-mail to: >>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>> Bug Reporting: support@webdna.us >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Donovan Brooke
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:
Cookie still not working (1999)
question: Eudora 3.1.1 (1997)
I give up!! (1997)
Expiration of Carts (1997)
[WebDNA] anybody installed on snow leopard (2009)
WebCatalog can't find database (1997)
WebCat Code and WebStar Search? (2000)
Document Contains No Data! (1997)
DON'T use old cart file! (1997)
notification solutions (1997)
RE: Languages (1997)
RE: PIXO support (1997)
[WebDNA] Still having problems (2008)
Spell Check (2005)
[WebDNA] Does [referrer] get lost when server switches from http (2020)
Triggers under Windows NT (2001)
Authorize.net questions ... (2003)
Pithy questions on webcommerce & siteedit (1997)
[Sum] function? (1997)
Separate server for jpg/gif files (1998)