This is a known issue. For best practices you should never use select *. There is no good business or coding reason to do so, it should be transparent what data you are asking for. I'm not sure if flushing the template cache will correct this. It is simple enough to test in a dev environment.
-----Original Message----- From: Brent Shaub [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 27, 2006 12:57 PM To: CF-Talk Subject: select * (star) caching Is this new to CF 7? I've got a handful of "select *" queries that when I modify the underlying table, the results do not include the new column(s). If this is a known issue, how can I refresh the cache for CF to pull the new fields? Since I inherited the app, listing all the columns and ideally reviewing which columns are needed (which is further time-consuming since many queries are in reused .cfcs) would be less than ideal. As part of new development rollouts, I'd just flush the cache after changing the database. Thanks in advance, Brent ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:254460 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
