Can't use direct SQL. I'm using a rather complex direct SQL call
already. Then I'm using @FILTER to narrow the found set more.
Sometimes there is a temp table created if the request is more
complex. Then it's stored as an array of just the values needed for
the sort. Then there is another SQL call to get the display columns
based off the unique ID of the 15 items in the array that are on a
"page". This actually is very fast with some rather large, indexed
TEXT type columns in the original SQL query. ;)
--
Beverly Voth
mailto:[EMAIL PROTECTED]
tel:(606) 864-0041
--
On Nov 4, 2008, at 12:05 AM, "D. Richardy" <[EMAIL PROTECTED]> wrote:
Beverly,
use a direct SQL-command to do the sort.
1) it's faster as Witango
2) it work
regards
Daniel
----- Original Message ----- From: "Beverly Voth" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, November 03, 2008 7:44 PM
Subject: Witango-Talk: Witango and @SORT for arrays
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
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
