I have also copped this problem every now and after adding new fields to a table and having cfqueryparam based queries die for no reason. In the past I have just changed the datasource in cfadmin to point to a non-existent database, saved this, then changed it back and resaved. This causes the datasource to be recreated and flushed, and the new table schema will then be accessible by cfqueryparam.
That "Maintain Connections" settings looks like a much more elegant solution as long as it has no undesired onflow effects. Cheers, Phil "Adam Chapman" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Hi Steve, I has this same scenario happen to me last week.. What is your cf admin "Maintain Connections" setting? I unchecked this option on my dev machine and it solved the issue. I dont know what flow on effect this change might have on your application? Cheers, Adam -----Original Message----- From: Steve Onnis [mailto:[EMAIL PROTECTED] Sent: Wednesday, 1 June 2005 11:22 AM To: CFAussie Mailing List Subject: [cfaussie] Re: CFQUERYPARAM - please explain Yeah it was strange If i manualy added the column to the query it was fine, but if i reverted back to the "*" then it went back to the original columns veeery strange -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sean Corfield Sent: Wednesday, June 01, 2005 11:14 AM To: CFAussie Mailing List Subject: [cfaussie] Re: CFQUERYPARAM - please explain 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/ --- 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/ --- 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/
