Re: Sorting Results
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 23465
interpreted = N
texte = I believe your code is correct except it thinks what you are sorting is textnot numbers. I included the related page from the docs (found underSearch/numbers) below.I hope it help.RH Proutybristol> I am having problems sorting results. The number 100 is listing below 99,> 98 ...>> Is there a formatting error in my search?>> [search db=[sku].db&eqnamedata=t&bidsort=1&bidsdir=de&max=3]>> Thanks,>> Arthur> http://www.educorp.comxxxxxxxxxx Docs xxxxxxxxxxxxSearching - NumbersFieldNametype=numWebCatalog normally compares all fields in a database as though they weretext, even if they look like numbers to you. Unless you tell it to compare afield numerically (or as a date), all comparisons are alphabetical.If your database has a numeric field (Price, for instance) that you wish tocompare numerically, you would put something like the following in thesearch criteria:http://Results.tpl?command=search&gePricedata=99.95&Pricetype=numWhy is this important? Imagine that WebCatalog is comparing two text fieldsthat happen to contain numbers in them:Compare 10.95 to 9.95 -- when compared alphabetically, WebCatalog looksat the first letter in both fields and sees 1 and 9, respectively. Inthis case, it would (wrongly) assume that 9 is greater than 1 (which inan alphabetical sense is true), and would sort 9.95 after 10.95. This isprobably not what you meant.When compared numerically, the two numbers would sort correctly.
Associated Messages, from the most recent to the oldest:
I believe your code is correct except it thinks what you are sorting is textnot numbers. I included the related page from the docs (found underSearch/numbers) below.I hope it help.RH Proutybristol> I am having problems sorting results. The number 100 is listing below 99,> 98 ...>> Is there a formatting error in my search?>> [search db=[sku].db&eqnamedata=t&bidsort=1&bidsdir=de&max=3]>> Thanks,>> Arthur> http://www.educorp.comxxxxxxxxxx Docs xxxxxxxxxxxxSearching - NumbersFieldNametype=numWebCatalog normally compares all fields in a database as though they weretext, even if they look like numbers to you. Unless you tell it to compare afield numerically (or as a date), all comparisons are alphabetical.If your database has a numeric field (Price, for instance) that you wish tocompare numerically, you would put something like the following in thesearch criteria:http://Results.tpl?command=search&gePricedata=99.95&Pricetype=numWhy is this important? Imagine that WebCatalog is comparing two text fieldsthat happen to contain numbers in them:Compare 10.95 to 9.95 -- when compared alphabetically, WebCatalog looksat the first letter in both fields and sees 1 and 9, respectively. Inthis case, it would (wrongly) assume that 9 is greater than 1 (which inan alphabetical sense is true), and would sort 9.95 after 10.95. This isprobably not what you meant.When compared numerically, the two numbers would sort correctly.
RH Prouty
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:
WebCat2 Append problem (B14Macacgi) (1997)
Problems with [Search] param - Mac Plugin b15 (1997)
Press Release hit the NewsWire!!! (1997)
Not really WebCat- (1997)
HTML authentication HTML page (1999)
Page Breaks in Word (2003)
Error.html (1997)
Mac 4.0b2 Installer Problems (2000)
Thanks Grant (1997)
Problems with SELECT MULTIPLE (1999)
SQL / Webcat Help (1999)
Exclude by date - multiple (1997)
YACBQ.....(Yet another checkbox question) (2000)
Re:E-mailer application times out (1998)
Suggestions on best way to work with yyyy/mm/dd (1997)
Re:no [search] with NT (1997)
Problems passing [SKU] with $Replace in 2.0 (1997)
Follow-Up to: Removing [showif] makes a big difference in speed (1997)
Nested tags count question (1997)
[WebDNA] agree? --> [url] broken inside [redirect], on a square-bracket-style include, included from a XML-style page (2009)