>Great suggestions...I almost have the Method=Get working...
>
>I like that idea about using JS to do it client side though also.
>I'll look into that.
>
>Thanks
>Rick
There's a really nice Javascript library that does sortable tables. It is very
unobstrusive and quite simple to set up - just set
If you've got a query like that, why store it in the SESSION? Store it in
the Application scope. Store it once and you're done.
-Original Message-
From: Jeff Guillaume [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 3:11 PM
To: CF-Talk
Subject: Re: Sorting by Colu
holy paranoia batman, that sounds scary!
checkout this from the redballoon folks
http://labs.redbd.net/blog/index.cfm/2006/8/8/Open-Source-Datagrid
nice html based datagrid easily built in a few minutes using customtags.
Has sorting, linking and filtering all in one simple ba!
DK
http://www.c
>>only recommend it if you know your result sets will always be
relatively small.
Better store the form fields in the session anyway:
if not isDefined ("url.sortBy")
Store the form structure in a session variable
else
restore the form structure from the session variable
endif
run the qu
Great suggestions...I almost have the Method=Get working...
I like that idea about using JS to do it client side though also.
I'll look into that.
Thanks
Rick
~|
Introducing the Fusion Authority Quarterly Update. 80 pages of har
Storing the results in SESSION is a nifty (and fast) method, but I'd only
recommend it if you know your result sets will always be relatively small. You
don't want 100 people caching a resultset of, say, 10,000 rows of data. You'll
run into memory issues.
~
The quickest fix would be to pass your search parameters on the URL instead of
FORM (action="get" instead of action="post" from the submitting page).
Then grab the current URL, minus the sort parameter, to re-use for the next
output.
Category
.etc.
This will retain the search parameters (s
Everett, Al (NIH/NIGMS) [C] wrote:
> Well, yeah, because the form variables don't exist because you're not
> submitting a form.
>
> There are a couple of ways I would attack this:
>
> 1. Cache the initial query to the session scope. Then do a query of
> query to sort when one of the headers is cl
It also wouldn't hurt to reference url.sortby instead of having it scope
hunt.
-Robert
-Original Message-
From: Everett, Al (NIH/NIGMS) [C] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 2:55 PM
To: CF-Talk
Subject: RE: Sorting by Column Headers
Well, yeah, because the
Well, yeah, because the form variables don't exist because you're not
submitting a form.
There are a couple of ways I would attack this:
1. Cache the initial query to the session scope. Then do a query of
query to sort when one of the headers is clicked.
2. Have the form use method="get" so that
Allow your code to accept the sort/filter variables as form or url
variables. For example, something like:
SELECT
col1,
col2
FROM
table
WHERE
col1 = '#FORM.Filter#'
11 matches
Mail list logo
