|
Bob's
Creedy's idea of breaking the lock with a failed SQL statement (within a CFQUERY
against the intended datasource) is the simplest way to break the lock. If
you can ask the admin to uncheck the "maintain db connections" for the
datasource, it would be easier for you (and believe it or not, there are MM KB
articles that suggest it's actually better for all kinds of reasons to leave it
unchecked).
What
Bob Keleher mentioned below as a tag is instead a function, so you could do a
<cfset tmp=CFUSION_DBCONNECTIONS_FLUSH()>. The nasty with that is that is
that it breaks the connections for ALL datasources on the server. If the admin
doesn't fix the setting for your datasource, let him/her know that you could
solve it this latter way. If s/he doesn't wake up and smell *that* coffee, you
might want to think about the quality of your administrator. :-) Sadly, they're
often pretty clueless about CF matters.
/charlie
|
- [CFTALKTor] Database Locks Mike
- Re: [CFTALKTor] Database Locks Bob Keleher
- Re: [CFTALKTor] Database Locks Mike
- Re: [CFTALKTor] Database Locks charles arehart
- Re: [CFTALKTor] Database Locks Bob Creedy
- [CFTALKTor] Database Locks Mike
