Re: Searching for the end

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 21507
interpreted = N
texte = >The exact thing i need to do is find the last 25 VURDERINGSNUMMER and sort >it by date in descending order, so the last comes first >But i can't get it to work :-{I think you *cannot* solve your problem until you create a field whose value is set at the time the record is created and whose value is larger than all the other values in the db.It's easy to use the [cart] tag for this task, because all you have to do is put fieldName=[cart] into your append context, and it will automatically create a unique value that's ALPHABETICALLY the largest value in the database (assuming you're not passing some other cart value to the page with the append context in it).Then you can do a search that retrieves all the records in the database (neSKUdatarq=[blank]) and limits the results to 25 records per founditems context (max=25) and sorts that field in descending order so the LAST 25 records will be the ones displayed (defieldNamesort=1).But right now, you don't have any field in your database that can be sorted in descending order and still retrieve the last 25 records. And any other sort you perform will result in having the records returned in a different order, not in reverse database order. So it seems you need to create a new field for the purpose of sorting in reverse-database order.It would be nice if PCS would consider making a new parameter that does this for us. We have rank=off to give us our results in database order --with no sorting at all -- but we have nothing to give us the results in reverse-database order.Perhaps a parameter like dbsort=reverse might be added to the WebDNA language, which would tell webcat to display the founditems in the OPPOSITE order from the way they appear in the db.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Associated Messages, from the most recent to the oldest:

    
  1. Re: Searching for the end (Brian Fries 1998)
  2. Re: Searching for the end (Gary Richter 1998)
  3. Re: Searching for the end (Martin Gertz Bech 1998)
  4. Re: Searching for the end (Kenneth Grome 1998)
  5. Re: Searching for the end (Martin Gertz Bech 1998)
  6. Re: Searching for the end (Dave MacLeay 1998)
  7. Re: Searching for the end (Martin Gertz Bech 1998)
  8. Re: Searching for the end (Kenneth Grome 1998)
  9. Re: Searching for the end (Dave MacLeay 1998)
  10. Searching for the end (Martin Gertz Bech 1998)
>The exact thing i need to do is find the last 25 VURDERINGSNUMMER and sort >it by date in descending order, so the last comes first >But i can't get it to work :-{I think you *cannot* solve your problem until you create a field whose value is set at the time the record is created and whose value is larger than all the other values in the db.It's easy to use the [cart] tag for this task, because all you have to do is put fieldName=[cart] into your append context, and it will automatically create a unique value that's ALPHABETICALLY the largest value in the database (assuming you're not passing some other cart value to the page with the append context in it).Then you can do a search that retrieves all the records in the database (neSKUdatarq=[blank]) and limits the results to 25 records per founditems context (max=25) and sorts that field in descending order so the LAST 25 records will be the ones displayed (defieldNamesort=1).But right now, you don't have any field in your database that can be sorted in descending order and still retrieve the last 25 records. And any other sort you perform will result in having the records returned in a different order, not in reverse database order. So it seems you need to create a new field for the purpose of sorting in reverse-database order.It would be nice if PCS would consider making a new parameter that does this for us. We have rank=off to give us our results in database order --with no sorting at all -- but we have nothing to give us the results in reverse-database order.Perhaps a parameter like dbsort=reverse might be added to the WebDNA language, which would tell webcat to display the founditems in the OPPOSITE order from the way they appear in the db.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net 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:

Is there a max number of fields? (1998) mass mailing and mass hysteria (1998) Error Page? (1997) WebCatalog NT beta 18 problem (1997) Re:[input] context (1999) Weird bug, or is there something amiss? (1997) Stop the madness. (1997) Dubble Sku's in a Database (1999) Item options w/ price adjustment (1997) Concatenating Form Variables (1998) Nested vs conditional (1997) Ok here is a question? (1997) Newbie problem blah blah blah (1997) Webcat interfering with Webstar? (1998) FWD: Autoproxy Bug with WebCatalog and FireSite (1997) Introduction/Tutorial/QuickStart (1997) [trim]?! (2004) Forcing Search w/ URL (1999) [WebDNA] Serial numbers and pricing for WebDNA 7.0 (2011) WebCatalog NT beta 18 problem (1997)