Re: Sorting Problems

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 55457
interpreted = N
texte = How 'bout this... Assuming you've got answers for the sorting issues posted by the others... Instead of directly dumping the data to the page within the founditems loop, stick them into a text variable, pre-pending the new record in front of the previously found records. After leaving the founditems, dump the text variable onto the page. Something like this: [text]tList=[/text] [search db=... allhit=1&RecordDatesort=1&RecordDatesdir=de&max=10] [founditems] [text]tList=[recorddate] [data]
[tList][/text] [/founditems] [/search] [tList] .... of course, [tList] could be filled with table rows or whatever you desire. The key is you're sticking the new record in the FRONT of the [tList] variable, before the previous records, so they will be displayed in reverse order of WebDNA's sorting. - brian On Jan 13, 2004, at 10:52 AM, Pat Holliday wrote: > Hi, > > I have records stored in a db that each have a date chosen by the user > - [RecordDate]. (I.e. the records all have a date but they are not > necessarily in the Db in date order - so rank=off won't work.) > > By default a user will view a page of records loaded with the > [RecordDate] most recent 10, although they can choose to view 20, 50 > or all matching records. > > The nature of the site requires that records appear on the page > horizontally, earliest first. > > eg: > > 5th Jansome data 1 > 6th Jansome data 2 > 10th Jansome data 3 > > To restrict my search to max=10 is easy and sort latest first > > RecordDatesort=1&RecordDatesdir=de > > is fine but the results come out "upside down": > > 10th Jansome data 3 > 6th Jansome data 2 > > etc > > Anyone think of an elegant solution to this problem? > > Thanks > > Pat > > ps something like this has been mentioned, seems a bit processor > intensive tho: > > [search > db=patsrecords.db&eqcriteriadata=[criteria]&RecordDatesort=1&RecordDate > sdir=as] > [text]OnlyShowIndex=[math][numfound]-[MaxRecords][/math][/text] > [founditems] > [hideif [index]<[OnlyShowIndex]] > Whatever > [/hideif] > [/founditems] > [/search] > > ...or sumfin...:) > > --------------------------------------------------------- > Netro42 - http://www.netro42.com > Web design and development -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Sorting Problems ( Toby Cox 2004)
  2. Re: Sorting Problems ( Brian Fries 2004)
  3. Re: Sorting Problems ( Glenn Busbin 2004)
  4. Re: Sorting Problems ( Pat Holliday 2004)
  5. Re: Sorting Problems ( Glenn Busbin 2004)
  6. Re: Sorting Problems ( Brian Fries 2004)
  7. Re: Sorting Problems ( Joe D'Andrea 2004)
  8. Re: Sorting Problems ( Gary Krockover 2004)
  9. Sorting Problems ( Pat Holliday 2004)
  10. Re: Sorting problems (Kenneth Grome 2000)
How 'bout this... Assuming you've got answers for the sorting issues posted by the others... Instead of directly dumping the data to the page within the founditems loop, stick them into a text variable, pre-pending the new record in front of the previously found records. After leaving the founditems, dump the text variable onto the page. Something like this: [text]tList=[/text] [search db=... allhit=1&RecordDatesort=1&RecordDatesdir=de&max=10] [founditems] [text]tList=[recorddate] [data]
[tList][/text] [/founditems] [/search] [tList] .... of course, [tList] could be filled with table rows or whatever you desire. The key is you're sticking the new record in the FRONT of the [tList] variable, before the previous records, so they will be displayed in reverse order of WebDNA's sorting. - brian On Jan 13, 2004, at 10:52 AM, Pat Holliday wrote: > Hi, > > I have records stored in a db that each have a date chosen by the user > - [RecordDate]. (I.e. the records all have a date but they are not > necessarily in the Db in date order - so rank=off won't work.) > > By default a user will view a page of records loaded with the > [RecordDate] most recent 10, although they can choose to view 20, 50 > or all matching records. > > The nature of the site requires that records appear on the page > horizontally, earliest first. > > eg: > > 5th Jansome data 1 > 6th Jansome data 2 > 10th Jansome data 3 > > To restrict my search to max=10 is easy and sort latest first > > RecordDatesort=1&RecordDatesdir=de > > is fine but the results come out "upside down": > > 10th Jansome data 3 > 6th Jansome data 2 > > etc > > Anyone think of an elegant solution to this problem? > > Thanks > > Pat > > ps something like this has been mentioned, seems a bit processor > intensive tho: > > [search > db=patsrecords.db&eqcriteriadata=[criteria]&RecordDatesort=1&RecordDate > sdir=as] > [text]OnlyShowIndex=[math][numfound]-[MaxRecords][/math][/text] > [founditems] > [hideif [index]<[OnlyShowIndex]] > Whatever > [/hideif] > [/founditems] > [/search] > > ...or sumfin...:) > > --------------------------------------------------------- > Netro42 - http://www.netro42.com > Web design and development -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Brian Fries

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:

Database Upload (2000) [WebDNA] [OT] - One Man. One Road. (2010) problems with WebCat-Plugin (1997) Re[2]: 2nd WebCatalog2 Feature Request (1996) [WebDNA] Windows server version vs WebDNA fastcgi in Mojave (2019) WebDNA 5 - Privacy Issue (Built in sniffer) (2003) Webcatalog not interpreting html pages (2002) A question on sub-categories (1997) Ken's grep question about renaming files to lowercase (2003) Unexpected error (1997) My solution... (1996) can you take a look #2 try (2003) [SHOWIF] PROBLEM (2000) RE: Credit card processing - UK (1997) Re:Help name our technology! (1997) Re: (1998) [WebDNA] Migration to linux/apache from IIS (2012) suffix mapping for NT? (1997) MacAuthorize order data fields WAS:How To question... (1997) Email (1998)