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 text not numbers. I included the related page from the docs (found under Search/numbers) below.I hope it help.RH Prouty bristol> 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 - Numbers FieldNametype=numWebCatalog normally compares all fields in a database as though they were text, even if they look like numbers to you. Unless you tell it to compare a field numerically (or as a date), all comparisons are alphabetical. If your database has a numeric field (Price, for instance) that you wish to compare numerically, you would put something like the following in the search criteria:http://Results.tpl?command=search&gePricedata=99.95&Pricetype=num Why is this important? Imagine that WebCatalog is comparing two text fields that happen to contain numbers in them: Compare 10.95 to 9.95 -- when compared alphabetically, WebCatalog looks at the first letter in both fields and sees 1 and 9, respectively. In this case, it would (wrongly) assume that 9 is greater than 1 (which in an alphabetical sense is true), and would sort 9.95 after 10.95. This is probably 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 text not numbers. I included the related page from the docs (found under Search/numbers) below.I hope it help.RH Prouty bristol> 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 - Numbers FieldNametype=numWebCatalog normally compares all fields in a database as though they were text, even if they look like numbers to you. Unless you tell it to compare a field numerically (or as a date), all comparisons are alphabetical. If your database has a numeric field (Price, for instance) that you wish to compare numerically, you would put something like the following in the search criteria:http://Results.tpl?command=search&gePricedata=99.95&Pricetype=num Why is this important? Imagine that WebCatalog is comparing two text fields that happen to contain numbers in them: Compare 10.95 to 9.95 -- when compared alphabetically, WebCatalog looks at the first letter in both fields and sees 1 and 9, respectively. In this case, it would (wrongly) assume that 9 is greater than 1 (which in an alphabetical sense is true), and would sort 9.95 after 10.95. This is probably 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:
Success Stories (1997)
WebCat2b13MacPlugIn - more [date] problems (1997)
emailer (1997)
Append command (2000)
[WebDNA] Retrieving a PDF from an email (2008)
Forms Search Questions (1997)
WC2b15 File Corruption (1997)
EIMS Problems (1997)
WebCat2b13 Command Reference Doc error (1997)
$Replace with [founditems] (1997)
Universal root for WC errors? (1997)
Stumpted Again (1997)
Help! WebCat2 bug (Ben's input) (1997)
PCS Customer submissions ? (1997)
Grouping search fields, etc. (1997)
Webcat 2.0.1 date math bug -> Crash! (1997)
For those of you not on the WebCatalog Beta... (1997)
[WriteFile] problems (1997)
Date Range search (1997)
2.0Beta Command Ref (can't find this instruction) (1997)