Re: Searching for the end
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 21511
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. Super Ken, webdna expert!!!! anyway to use the index value of the records to do this? I have no idea if this is even possible other then showing the index value on the screen or dividing by it for the tables stuff. But I thought I would toss it out into the mix for your thought process.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
Associated Messages, from the most recent to the oldest:
>>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. Super Ken, webdna expert!!!! anyway to use the index value of the records to do this? I have no idea if this is even possible other then showing the index value on the screen or dividing by it for the tables stuff. But I thought I would toss it out into the mix for your thought process.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com ===============================================
Gary Richter
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:
This message couldn't reach the list! (multi-column (1998)
Return as Delimeter (2000)
WebCat2b13MacPlugIn - [include] (1997)
A few questions. . . (1997)
Email Not Being Sent (2004)
Search in 2 or more catalogs (1997)
filtering [founditems] (2004)
Prepaid monthly subscription order fulfillment question (2004)
WebDNA on Apache/Xserve (2003)
Basics of tcpconnect (2006)
Using [Include] Context (1999)
Purchae error - Fixed to a degree (1997)
Electronic Delivery (1997)
OFF TOPIC - sendmail problem (2003)
international time (1997)
[append] and SSL (1997)
Frames and WebCat (1997)
A little syntax help (1997)
WebCat cannot handle compatible search parameters? (1997)
CPU Usage 165% (2005)