The easiest way to update cached queries is:
Use the cachedafter parameter on all queries to reference an application
variable (one variable for each table or set of tables used together)
When doing a SELECT query, set the variable to now() if it is
blank, otherwise
the last setting is used
When doing an UPDATE or DELETE query, reset the application variable to
now(), thus resetting the cache (the next request will not be cached)
HTH
Dick
At 10:13 AM -0800 11/24/00, paul smith wrote:
>We use them a LOT. They're terrific! We started out storing data in
>Structures and switched to cached queries. The only Con I can think of
>right now is how to update them (but this is not a problem for my
>application where I can just re-start CF). Pre-4.5 CF Administrator
>suggested there was a limit of 100, but this is an error. The only limit I
>know of is available RAM and 9999 (which is the largest number you can
>insert in the CF Administrator).
>
>best, paul
>
>At 05:13 AM 11/23/00 +0000, you wrote:
>>Does anyone have any experience with caching queries??? I am looking for
> >some pros & cons from others experiences with caching queries. TIA
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
