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:
[WebDNA] CDATA in XML = blank value (2015)
Individual Tax on Items (1998)
Re1000001: Setting up shop (1997)
New Image Gallery using WebDNA and ImageMagick (2003)
Summing a field full of numbers ... (1997)
forms (2001)
Separate SSL Server (1997)
Insert Line Feed Character (2004)
Sorting error (1997)
Draft Manual, Tutorial, and more (1997)
FM 4.1 and Webcat? (1998)
bug in [SendMail] (1997)
Upgrading old WebCat Database Files (1997)
[WriteFile] problems (1997)
Shop from PDF (2004)
Cart Transfer from Un-Secure to Secure (2000)
Error Lob.db records error message not name (1997)
Session Number (1998)
Make sure I understand this??? (1997)
Urgent help needed (1998)