So, I've discovered that CF seems to be caching queries whether or not I
want it to. So, for instance, I have a query like so:
SELECT *
FROM Y
If Y is a view and I change the view to add a new column, I have to add
something like
WHERE 1=1
to force it to see the new view.
If I take the WHERE 1=1 back off, it reverts to the old view again.
We don't have trusted cache turned on. This is on a dev box, set up to be as
"dynamic" as possible.
Does CFMX internally convert the * to a column list that gets cached?
(Yes, yes, I know that * is not a best practice unless you're really using
all the columns. But, really, I'm using all the columns. Every single one.
All 86 computed columns of the query. That's why I created the view.)
--
Deanna Schneider
UWEX-Cooperative Extension
Interactive Media Developer
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
