Re: [WebDNA] Sort Direction matches the written to file order

This WebDNA talk-list message is from

2015


It keeps the original formatting.
numero = 112101
interpreted = N
texte = --Apple-Mail=_6F980320-BE67-456A-889C-5A97E0BC87B7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Palle You could rewrite the dbs with the new field. But I agree, expansion of rank=3D=E2=80=9Coff=E2=80=9D would be good. Out of interest have you tried to see if rank=3D=E2=80=9Casc=E2=80=9D & = rank=3D=E2=80=9Cdes=E2=80=9D work - they may be undocumented. Kind regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > On 11 Feb 2015, at 6:53 pm, Palle Bo Nielsen = wrote: >=20 > Hi Stuart >=20 > Thanks - all though I am aware of the Autonumber functionality, it = only works when a new row is written to DB and I have have several = DB=E2=80=99s without any chronological index=E2=80=99es unfortunately. I = could develop a mechanism which populates all my DB=E2=80=99s (one by = one) which populates them using the Autonumber function, but it would be = a hassle an take a lot of time to process. A build in =E2=80=98Reverse=3DT= rue=E2=80=99 would be a perfect solution.=20 >=20 > Is still see the need of a WebDNA Function which can help here... >=20 >=20 > Palle...: >> Wouldn=E2=80=99t it be logical if the reverse approach were = achievable >> also instead of doing a TABLE and then REVERSE the output? >=20 > Kenneth Grome...: > Absolutely, and this is something I have wished for forever. > Something as simple as "reverse=3DT" to be interpreted only when > "rank=3Doff" is used might be an easy way to do it. >=20 >=20 > Christophe. What is your view on this challenge/possibility? >=20 > /Palle >=20 >=20 >=20 >=20 >=20 >> On 10/02/2015, at 23.24, Stuart Tremain > wrote: >>=20 >> Put another field in you db named SORTORDER which could be populated = AUTONUMBER=3DSORTORDER this will be populated from 1 - n >>=20 >> Then just do a normal sort on SORTORDER >>=20 >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 11 Feb 2015, at 2:49 am, Palle Bo Nielsen = > wrote: >>>=20 >>> I agree. >>>=20 >>> But some of my index mechanism are not chronologic and as such can = not be used. Like for instance [cart] which sometimes ads a character or = two extra. >>>=20 >>> The WebDNA core functionality would be very helpful here. >>>=20 >>> /Palle >>>=20 >>>=20 >>>> On 10/02/2015, at 16.45, Stephen Reiss > wrote: >>>>=20 >>>> You could always add an index number to the records. That would = make it simple to sort in either direction. >>>>=20 >>>>=20 >>>>=20 >>>> On Feb 10, 2015, at 12:43 PM, Palle Bo Nielsen = > wrote: >>>>=20 >>>>> Hi Tom >>>>>=20 >>>>> That did the trick, thanks. >>>>>=20 >>>>> Wouldn=E2=80=99t it be logical if the reverse approach were = achievable also in stead of doing a TABLE and then REVERSE the output? >>>>>=20 >>>>> I often work with databases with more than one million rows and = multiple fields associated and it would be a hassle to do that kind of = work around and a waste of memory. >>>>>=20 >>>>> Christophe, are you aware of an easier solution or could the = Reverse Sorting order be a candidate for the next WebDNA release. I find = this very attractive=E2=80=A6 Any opinion from any other on the List? >>>>>=20 >>>>> /Palle >>>>>=20 >>>>>=20 >>>>>=20 >>>>>> On 10/02/2015, at 15.52, Tom Duke > wrote: >>>>>>=20 >>>>>> Palle, >>>>>>=20 >>>>>> Hi - my recollection is that you don't specify a sort order but = do add "&rank=3Doff" to the search string. Then the data should display = as written in the db. >>>>>>=20 >>>>>> You would probably have to generate a table in reverse order and = search that to get the reversed order. >>>>>>=20 >>>>>> - Tom >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >>>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us = ------------------------------------------------= --------- This message is sent to you because you are subscribed to the = mailing list . To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --Apple-Mail=_6F980320-BE67-456A-889C-5A97E0BC87B7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Palle

You = could rewrite the dbs with the new field.

But I agree, expansion of = rank=3D=E2=80=9Coff=E2=80=9D would be good.

Out of interest have you tried to see = if rank=3D=E2=80=9Casc=E2=80=9D & rank=3D=E2=80=9Cdes=E2=80=9D work = - they may be undocumented.


Kind regards

Stuart Tremain
IDFK Web Developments
AUSTRALIA





On 11 Feb 2015, at 6:53 pm, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

Hi Stuart

Thanks - all though I am aware of the Autonumber = functionality, it only works when a new row is written to DB and I have = have several DB=E2=80=99s without any chronological index=E2=80=99es = unfortunately. I could develop a mechanism which populates all my DB=E2=80= =99s (one by one) which populates them using the Autonumber function, = but it would be a hassle an take a lot of time to process. A build in = =E2=80=98Reverse=3DTrue=E2=80=99 would be a perfect = solution. 

Is still see the need of a WebDNA Function which can help = here...


Palle...:
Wouldn=E2=80=99t it be = logical if the reverse approach were achievable
also = instead of doing a TABLE and then REVERSE the output?

Kenneth = Grome...:
Absolutely, and this is something I have wished = for forever.
Something as simple as "reverse=3DT" to be = interpreted only when
"rank=3Doff" is used might be an = easy way to do it.


Christophe. What is your = view on this challenge/possibility?

/Palle





On = 10/02/2015, at 23.24, Stuart Tremain <webdna@idfk.com.au> = wrote:

Put another = field in you db named SORTORDER which could be populated = AUTONUMBER=3DSORTORDER this will be populated from 1 - n

Then just do a normal = sort on SORTORDER


Kind regards

Stuart Tremain
IDFK Web = Developments
AUSTRALIA





On 11 Feb 2015, at 2:49 am, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

I agree.

But some of my index mechanism are not chronologic and as = such can not be used. Like for instance [cart] which sometimes ads a = character or two extra.

The WebDNA core functionality would be very helpful = here.

/Palle


On 10/02/2015, at 16.45, Stephen Reiss <wineguy@mac.com> = wrote:

You could always = add an index number to the records. That would make it simple to sort in = either direction.



On Feb 10, 2015, at 12:43 PM, Palle Bo Nielsen = <powerpalle@powerpalle.dk> wrote:

Hi = Tom

That did = the trick, thanks.

Wouldn=E2=80=99t it be logical if the reverse approach were = achievable also in stead of doing a TABLE and then REVERSE the = output?

I = often work with databases with more than one million rows and multiple = fields associated and it would be a hassle to do that kind of work = around and a waste of memory.

Christophe, are you aware of an easier = solution or could the Reverse Sorting order be a candidate for the next = WebDNA release. I find this very attractive=E2=80=A6 Any opinion from = any other on the List?

/Palle



On 10/02/2015, at 15.52, Tom = Duke <tom@revolutionaries.ie> wrote:

Palle,

Hi = - my recollection is that you don't specify a sort order but do add = "&rank=3Doff" to the search string.  Then the data should = display as written in the db.

You would probably have to generate a = table in reverse order and search that to get the reversed = order.

- = Tom



--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
= --Apple-Mail=_6F980320-BE67-456A-889C-5A97E0BC87B7-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Sort Direction matches the written to file order (christophe.billiottet@webdna.us 2015)
  2. Re: [WebDNA] Sort Direction matches the written to file order (Palle Bo Nielsen 2015)
  3. Re: [WebDNA] Sort Direction matches the written to file order (Stuart Tremain 2015)
  4. Re: [WebDNA] Sort Direction matches the written to file order (Palle Bo Nielsen 2015)
  5. Re: [WebDNA] Sort Direction matches the written to file order (Stuart Tremain 2015)
  6. Re: [WebDNA] Sort Direction matches the written to file order (Kenneth Grome 2015)
  7. Re: [WebDNA] Sort Direction matches the written to file order (Palle Bo Nielsen 2015)
  8. Re: [WebDNA] Sort Direction matches the written to file order (Stephen Reiss 2015)
  9. Re: [WebDNA] Sort Direction matches the written to file order (Palle Bo Nielsen 2015)
  10. Re: [WebDNA] Sort Direction matches the written to file order (Tom Duke 2015)
  11. [WebDNA] Sort Direction matches the written to file order (Palle Bo Nielsen 2015)
--Apple-Mail=_6F980320-BE67-456A-889C-5A97E0BC87B7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Palle You could rewrite the dbs with the new field. But I agree, expansion of rank=3D=E2=80=9Coff=E2=80=9D would be good. Out of interest have you tried to see if rank=3D=E2=80=9Casc=E2=80=9D & = rank=3D=E2=80=9Cdes=E2=80=9D work - they may be undocumented. Kind regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au > On 11 Feb 2015, at 6:53 pm, Palle Bo Nielsen = wrote: >=20 > Hi Stuart >=20 > Thanks - all though I am aware of the Autonumber functionality, it = only works when a new row is written to DB and I have have several = DB=E2=80=99s without any chronological index=E2=80=99es unfortunately. I = could develop a mechanism which populates all my DB=E2=80=99s (one by = one) which populates them using the Autonumber function, but it would be = a hassle an take a lot of time to process. A build in =E2=80=98Reverse=3DT= rue=E2=80=99 would be a perfect solution.=20 >=20 > Is still see the need of a WebDNA Function which can help here... >=20 >=20 > Palle...: >> Wouldn=E2=80=99t it be logical if the reverse approach were = achievable >> also instead of doing a TABLE and then REVERSE the output? >=20 > Kenneth Grome...: > Absolutely, and this is something I have wished for forever. > Something as simple as "reverse=3DT" to be interpreted only when > "rank=3Doff" is used might be an easy way to do it. >=20 >=20 > Christophe. What is your view on this challenge/possibility? >=20 > /Palle >=20 >=20 >=20 >=20 >=20 >> On 10/02/2015, at 23.24, Stuart Tremain > wrote: >>=20 >> Put another field in you db named SORTORDER which could be populated = AUTONUMBER=3DSORTORDER this will be populated from 1 - n >>=20 >> Then just do a normal sort on SORTORDER >>=20 >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 11 Feb 2015, at 2:49 am, Palle Bo Nielsen = > wrote: >>>=20 >>> I agree. >>>=20 >>> But some of my index mechanism are not chronologic and as such can = not be used. Like for instance [cart] which sometimes ads a character or = two extra. >>>=20 >>> The WebDNA core functionality would be very helpful here. >>>=20 >>> /Palle >>>=20 >>>=20 >>>> On 10/02/2015, at 16.45, Stephen Reiss > wrote: >>>>=20 >>>> You could always add an index number to the records. That would = make it simple to sort in either direction. >>>>=20 >>>>=20 >>>>=20 >>>> On Feb 10, 2015, at 12:43 PM, Palle Bo Nielsen = > wrote: >>>>=20 >>>>> Hi Tom >>>>>=20 >>>>> That did the trick, thanks. >>>>>=20 >>>>> Wouldn=E2=80=99t it be logical if the reverse approach were = achievable also in stead of doing a TABLE and then REVERSE the output? >>>>>=20 >>>>> I often work with databases with more than one million rows and = multiple fields associated and it would be a hassle to do that kind of = work around and a waste of memory. >>>>>=20 >>>>> Christophe, are you aware of an easier solution or could the = Reverse Sorting order be a candidate for the next WebDNA release. I find = this very attractive=E2=80=A6 Any opinion from any other on the List? >>>>>=20 >>>>> /Palle >>>>>=20 >>>>>=20 >>>>>=20 >>>>>> On 10/02/2015, at 15.52, Tom Duke > wrote: >>>>>>=20 >>>>>> Palle, >>>>>>=20 >>>>>> Hi - my recollection is that you don't specify a sort order but = do add "&rank=3Doff" to the search string. Then the data should display = as written in the db. >>>>>>=20 >>>>>> You would probably have to generate a table in reverse order and = search that to get the reversed order. >>>>>>=20 >>>>>> - Tom >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >>>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us = ------------------------------------------------= --------- This message is sent to you because you are subscribed to the = mailing list . To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --Apple-Mail=_6F980320-BE67-456A-889C-5A97E0BC87B7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Palle

You = could rewrite the dbs with the new field.

But I agree, expansion of = rank=3D=E2=80=9Coff=E2=80=9D would be good.

Out of interest have you tried to see = if rank=3D=E2=80=9Casc=E2=80=9D & rank=3D=E2=80=9Cdes=E2=80=9D work = - they may be undocumented.


Kind regards

Stuart Tremain
IDFK Web Developments
AUSTRALIA





On 11 Feb 2015, at 6:53 pm, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

Hi Stuart

Thanks - all though I am aware of the Autonumber = functionality, it only works when a new row is written to DB and I have = have several DB=E2=80=99s without any chronological index=E2=80=99es = unfortunately. I could develop a mechanism which populates all my DB=E2=80= =99s (one by one) which populates them using the Autonumber function, = but it would be a hassle an take a lot of time to process. A build in = =E2=80=98Reverse=3DTrue=E2=80=99 would be a perfect = solution. 

Is still see the need of a WebDNA Function which can help = here...


Palle...:
Wouldn=E2=80=99t it be = logical if the reverse approach were achievable
also = instead of doing a TABLE and then REVERSE the output?

Kenneth = Grome...:
Absolutely, and this is something I have wished = for forever.
Something as simple as "reverse=3DT" to be = interpreted only when
"rank=3Doff" is used might be an = easy way to do it.


Christophe. What is your = view on this challenge/possibility?

/Palle





On = 10/02/2015, at 23.24, Stuart Tremain <webdna@idfk.com.au> = wrote:

Put another = field in you db named SORTORDER which could be populated = AUTONUMBER=3DSORTORDER this will be populated from 1 - n

Then just do a normal = sort on SORTORDER


Kind regards

Stuart Tremain
IDFK Web = Developments
AUSTRALIA





On 11 Feb 2015, at 2:49 am, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

I agree.

But some of my index mechanism are not chronologic and as = such can not be used. Like for instance [cart] which sometimes ads a = character or two extra.

The WebDNA core functionality would be very helpful = here.

/Palle


On 10/02/2015, at 16.45, Stephen Reiss <wineguy@mac.com> = wrote:

You could always = add an index number to the records. That would make it simple to sort in = either direction.



On Feb 10, 2015, at 12:43 PM, Palle Bo Nielsen = <powerpalle@powerpalle.dk> wrote:

Hi = Tom

That did = the trick, thanks.

Wouldn=E2=80=99t it be logical if the reverse approach were = achievable also in stead of doing a TABLE and then REVERSE the = output?

I = often work with databases with more than one million rows and multiple = fields associated and it would be a hassle to do that kind of work = around and a waste of memory.

Christophe, are you aware of an easier = solution or could the Reverse Sorting order be a candidate for the next = WebDNA release. I find this very attractive=E2=80=A6 Any opinion from = any other on the List?

/Palle



On 10/02/2015, at 15.52, Tom = Duke <tom@revolutionaries.ie> wrote:

Palle,

Hi = - my recollection is that you don't specify a sort order but do add = "&rank=3Doff" to the search string.  Then the data should = display as written in the db.

You would probably have to generate a = table in reverse order and search that to get the reversed = order.

- = Tom



--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
= --Apple-Mail=_6F980320-BE67-456A-889C-5A97E0BC87B7-- Stuart Tremain

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:

form data submission gets truncated (1997) WebCatalog can't find database (1997) WebCat2b13MacPlugIn - [include] (1997) For those of you not on the WebCatalog Beta... (1997) Location of Browser Info.txt file (1997) WebCat with WebTen (1998) cart ID (1998) Configuring E-mail (1997) Bad creator codes which cause access denied errormessage (1997) My X-Mas Wish (1999) WebDNA & HTML Problems (2003) Download URL & access on the fly ? (1997) different browser, different result (2000) [shownext max (1997) Random question (1998) [ConvertChars] problem (1997) Disappearing HTML/WebDNA (1998) Looking for WebCatalog Programmer in Silicon Valley (1998) Re:Merging databases (1997) WebCat2 - [format thousands] (1997)