On 5/31/05, Steve Onnis <[EMAIL PROTECTED]> wrote: > Can someone tell me how CFQUERYPARAM actually works?
Your problem is not to do with <cfqueryparam>... > SELECT col1, col2, col3 > FROM Table > WHERE ID = <cfqueryparam value="#Arguments.ID#" > cfsqltype="CF_SQL_INTEGER"> > > I then added an extra column to the table > > I then changed the query to > /////////////////////////////////// > SELECT * > FROM Table > WHERE ID = <cfqueryparam value="#Arguments.ID#" > cfsqltype="CF_SQL_INTEGER"> The structure of the table was already cached somewhere in the JDBC layer. If you change the SQL to SELECT col1,col2,col3,col4 ... that might be enough to refresh the internal cache. Or it might not. This is all to do with how the table metadata is managed in the JDBC layer I believe. Not quite sure how you flush the metadata tho', sorry. -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
