Re: Request for improvement...

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 44520
interpreted = N
texte = I know, that's how I've been working around the problem -- for a long time.But the fact remains, it is very confusing -- and still undocumented -- that the SORT parameters actually limit the ability to use certain SEARCH comparison operators.It is totally non-intuitive and completely unexpected that a parameter which is defined in the docs as a SORT parameter should have any effect on the ability to perform specific types of SEARCHES. But that is exactly the limitation that occurs.If the excuse for not fixing the problem is because there's already a work-around available, then the obligation of the company should be to explain the work-around in the docs. In fact, they should do more than just explain the work-around in the docs ... they SHOULD explain how the sort parameters actually alters the search and potentially makes the search fail.Bad and incomplete documentation with the webdna software creates as many problems as the bugs ... :( >You can define that field as a GROUPfield > >Ie group1field=first_field&group1type=date etc... > >Works great.. - has for a long time... > >On 10/29/02 5:05 PM, Kenneth Grome wrote: > >> It would be nice if we could define a field as a DATE field for >> sorting purposes only -- while also searching the same field with a >> bw comparison operator -- yet this is impossible in all current and >> previous versions of webdna. >> >> All I want is to store my dates in MM/DD/YYYY format, then I want to >> search with the bw operator so I can retrieve only certain months >> of records, and I want my results sorted as dates -- not as text. >> >> Why can't webdna handle this simple task? >> >> As soon as I use the fieldType=DATE parameter, I can no longer do a >> bw comparison on the same field. I guess I do not understand why >> a SORT parameter has to limit the types of comparisons we can do in >> the SEARCH ... >> >> Is there anything that can be done to eliminate this problem? >> >> >> Sincerely, >> Kenneth Grome >> > >Jay Van Vark >'Guiding Positive Change in High-Tech Companies' >one box voicemail (866) 248-7670 x 6471 >efax (801) 659-7952 > >-- Great tool for advertising bid optimization, check out: >http://www.Promote4Less.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/Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- 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:

    
  1. Re: Request for improvement... (Stuart Tremain 2002)
  2. Re: Request for improvement... (Kenneth Grome 2002)
  3. Re: Request for improvement... (Jay Van Vark 2002)
  4. Request for improvement... (Kenneth Grome 2002)
I know, that's how I've been working around the problem -- for a long time.But the fact remains, it is very confusing -- and still undocumented -- that the SORT parameters actually limit the ability to use certain SEARCH comparison operators.It is totally non-intuitive and completely unexpected that a parameter which is defined in the docs as a SORT parameter should have any effect on the ability to perform specific types of SEARCHES. But that is exactly the limitation that occurs.If the excuse for not fixing the problem is because there's already a work-around available, then the obligation of the company should be to explain the work-around in the docs. In fact, they should do more than just explain the work-around in the docs ... they SHOULD explain how the sort parameters actually alters the search and potentially makes the search fail.Bad and incomplete documentation with the webdna software creates as many problems as the bugs ... :( >You can define that field as a GROUPfield > >Ie group1field=first_field&group1type=date etc... > >Works great.. - has for a long time... > >On 10/29/02 5:05 PM, Kenneth Grome wrote: > >> It would be nice if we could define a field as a DATE field for >> sorting purposes only -- while also searching the same field with a >> bw comparison operator -- yet this is impossible in all current and >> previous versions of webdna. >> >> All I want is to store my dates in MM/DD/YYYY format, then I want to >> search with the bw operator so I can retrieve only certain months >> of records, and I want my results sorted as dates -- not as text. >> >> Why can't webdna handle this simple task? >> >> As soon as I use the fieldType=DATE parameter, I can no longer do a >> bw comparison on the same field. I guess I do not understand why >> a SORT parameter has to limit the types of comparisons we can do in >> the SEARCH ... >> >> Is there anything that can be done to eliminate this problem? >> >> >> Sincerely, >> Kenneth Grome >> > >Jay Van Vark >'Guiding Positive Change in High-Tech Companies' >one box voicemail (866) 248-7670 x 6471 >efax (801) 659-7952 > >-- Great tool for advertising bid optimization, check out: >http://www.Promote4Less.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/Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- 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/ Kenneth Grome

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:

Which GUI HTML editors work with WC ? (1997) Feature req. (2002) Cumulative Shipping charge calculations - your help please. (1997) File not found error message (1998) Database Options (1997) Recording size of uploaded file? (2001) New York City sales tax database needed (1997) [redirect] w/o showing args? (1999) printing twice? and fix (1997) Secure server question (1997) headers (2000) WebCatalog can't find database (1997) Online Docs? (1997) carriage returns in data (1997) [Q] Novice's question (1997) [WebDNA] WebDNA developer (2008) Time code! (2002) Email (1998) Coding Standards - are there any ? (2003) Need Sample Template - just purchased (1997)