Re: [WebDNA] sort parameters in search
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 111847
interpreted = N
texte = 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.=20So.. 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.=20Note, 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.=20Sincerely,DonovanOn Jan 12, 2015, at 10:16 AM, Terry Wilson
wrote:> 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
Associated Messages, from the most recent to the oldest:
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.=20So.. 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.=20Note, 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.=20Sincerely,DonovanOn Jan 12, 2015, at 10:16 AM, Terry Wilson wrote:> 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
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:
Re:trouble (1997)
Clearly.home (1998)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
Add to Cart & List of Products (1997)
Weird problems with [SHOWIF]s (1997)
Frames (1997)
PROBLEM (1997)
REPOST: How do _you_ back up your db? (2000)
Validation (2000)
shipCost (1998)
[/application] error? (1997)
Dummy Credit Card Number for debug? (1997)
Getting Dreamweaver MX ( DW MX ) to play nicely with .TPL files (2003)
More Applescript (1997)
Sorting Problems (2004)
REPLACE & MAX/STARTAT parameters doesn't work? (2000)
WebDNA 5.0 Enterprise Edition (2003)
Re2: AAgghh!! Help, please. SSL strikes again. (1997)
DON'T use old cart file! (1997)
Maybe Off Topic -- OS X/UNIX Shell Scripts? (2003)