Would that have something to do with the error I get if I run a query
using <cfqueryparam> , make a slight change to database structure and
then run the query again? If I remove the <cfqueryparam> it works fine
and if I wait awhile before running the query again it does fine.
Almost acts like it's caching info that is no longer correct following
a slight change to the table.

Ken

On Wed, 22 Sep 2004 01:48:50 -0700, Paul Kenney <[EMAIL PROTECTED]> wrote:
> Well, it does do the same thing. The only difference is that you use
> <cfquery> instead of using the JDBC API directly.  In fact, if you use
> <cfqueryparam>, the database turns your query is turned into a
> prepared statement the first time it is called and sends back a handle
> to the JDBC driver.  For all subsequent calls to that query, only the
> handle and the bound parameters are sent to the database--not the
> entire query.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to