Hi, all...

I've just begun using "cachedwithin" and ran into an issue
when running an insert query (not the one with the "cachedwithin" setting).

I got a duplicate key error.  I traced that down to the fact that I had
used "cachedwithin" on another query (a select query) with a different name 
that involved the
same data as the above mentioned insert query.

Once I ran the select query with a cachedwithin setting of 0, the cache 
apparently cleared
and the other insert query ran without any error.

My question is this:  How does the "cachedwithin" setting work with data?  I 
was under the
(false) assumption that the data involved would be tied to the name of the 
query which used
the "cachedwithin" setting.

However, I now see that caching data, even in a different query that involves 
the same data
can cause prolems.

Do I have to empty the cache every time I run a new insert query involving data 
that has been
cached somewhere else?

This could get complicated.  The "cachedwithin" setting is only shaving about 1 
second off
query results... from 2-3 for query and display, down to about 2 seconds.  I'm 
wondering if
having to run a query using "cachedwithin" with a 0 setting every time I want 
to insert
data is worth it.

Thoughts on this, anyone?

Thanks,

Rick



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to 
date
Get the Free Trial
http://ad.doubleclick.net/clk;192386516;25150098;k

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:304294
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to