I don't know if this is related, but there is a (long reported) bug in
Witango where sorts applied to user scoped variables don't "take".
(The sort persists once the array is sorted, however.)
So we sort as request scope, then save out as user scope...
and if we have to re-do a scope on user$array, we save it out in
request scope, sort, and re-save it back into user scope. It's a bit
clunky, but does work.
On [Nov 3 -2008 ], at 1:44 PM, Beverly Voth wrote:
I have a large solution that worked well until "SORTING" a list was
requested.
We make the SQL query and it's stored in an array (because it's far to
complex to requery to get the "next 15" set of records for the list
display).
So a link on the list page is passing the sortType to be performed
and an
@IF tests for the sortType. It then performs an <@SORT ARRAY....> on
the
columns requested.
It "seems" to work the first time you sort. However, from there it's
too
strange. Is the SORT actually re-arranging the ARRAY? And why would
it not
allow more than one sort action on the same array?
Thanks,
Beverly
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
