Augggh! You are NoT seeing the problem here... stored procs only get called
when CF asks for 'em. If CF request for a query that is cached, the db NeVeR
GeTs HiT...
BTW, I use stored procs extensively.
My solution can be used for data that changes constantly, and dynamically!
Forget scheduled apps, forget stored procs, and follow along carefully...
In a clustered webserver environment, if you are using the CACHEDWITHIN
attribute in a CFQUERY, there is no way for one node in the cluster to
notify the other nodes in a cluster of the need to refresh an existing
cached query.
In most cases, updates to data occur much less frequently than simple
queries against data. Registry hits are also quicker than a DB query.
My strategy is to have CF do an initial call to the Registry to get the time
value for the CACHEDWITHIN attribute, before any query.
The underlying theory is: It is faster to do a single Registry hit to get
the CACHEDWITHIN value than it is to run an uncached query; even if the
backside DB has a fancy stored proc.
If the data is being modified, the node doing the modifying does a remote
registry update to ALL the nodes in the cluster, changing a registry key
that holds the CACHEDWITHIN time for that particular query.
I've tested this, it works great.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
{redacted}You should use stored procedures, because they are
> designed to effeciently request and recieve the data, on a real time
> basis.
{redacted}
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
