Thanks for that, Mark - just what I needed. Cheers Terry
----------Original Message--------- > > >So you're saying, Mark, that there is an implicit lock on any variable > >that is read into a stored procedure, and that I can dispense with the > ><cflock>? > > Nope, I'm saying that you are creating a read lock unnecessarily around > a call to a stored procedure, which means while the stored procedure is > executing, no other code can write to 'this' session scope. > > I'd do something like this instead... > <cflock ...> > <cfset variables.userid = session.userid> > </cflock> > <cfstoredproc ...> > <cfprocpraram ... value="#variables.userid#"> > </cfstoredproc> > > Most users are unlikely to be multitasking on a site to the extent that > your code will cause problems, but I wouldn't do it (especially if > you've seen the copy 'n' paste junkies in action - change that variable > to be one in application scope and it's a different ball game). > > > Mark > > -- These lists are syncronised with the CFDeveloper forum at http://forum.cfdeveloper.co.uk/ Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ CFDeveloper Sponsors and contributors:- *Hosting and support provided by CFMXhosting.co.uk* :: *ActivePDF provided by activepdf.com* *Forums provided by fusetalk.com* :: *ProWorkFlow provided by proworkflow.com* *Tutorials provided by helmguru.com* :: *Lists hosted by gradwell.com* To unsubscribe, e-mail: [EMAIL PROTECTED]
