How is caching the query different from saving it as a session variable?
Both are kept in memory, right? Except that the cached one will get bumped
if memory is needed?
-----Original Message-----
From: Bob Silverberg [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 07, 2000 8:31 AM
To: CF-Talk
Subject: FW: passing cfquery results to another page
I had another thought. Just cache the query, and, as long as it doesn't get
bumped out of memory, it will be available on every page without having to
requery the database (you'd still issue the CFQUERY, but it wouldn't need to
hit the database). This will only work if you have a limited number of
query combinations, otherwise the chances of it getting bumped out of memory
are greater.
Bob
-----Original Message-----
From: Bob Silverberg [mailto:[EMAIL PROTECTED]]
Sent: December 7, 2000 10:19 AM
To: [EMAIL PROTECTED]
Subject: RE: passing cfquery results to another page
There are a number of ways, the first two that come to mind are:
1. Store it in a session variable.
2. Convert it to a WDDX packet, then store it in a client or cookie
variable, or pass it via a URL or form parameter. The last two aren't
advisable if the query is of any reasonable size.
Bob
-----Original Message-----
From: sam sidhom [mailto:[EMAIL PROTECTED]]
Sent: December 7, 2000 9:42 AM
To: CF-Talk
Subject: passing cfquery results to another page
Can anyone tell me if there is anyway CF will pass the results of a CFQuery
to another page without having to requery the database?
Thanks,
Jennifer Johnson
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
