On Thursday 11 Nov 2004 17:51 pm, Michael Dinowitz wrote:
> Very interesting. I'd never have thought of doing a var set before the
> CFQUERY. It would show up in my head as an unnecessary operation.
Yeah, I know.
When it was discovered you needed to do this (for thread safety) it was
suggested t
Just had a long talk with Sean about that. Not do-able (other than it looking
ugly). Doing an initial CFSET with the var key word is the way to go.
Especially since all the var declarations must be at the beginning of the
function.
--
Ian Skinner
Web Programmer
BloodSource
www.Bloo
It's one of those rare issues where you spend a few minutes to a few days
trying to find out why a value is being set one way when it's supposed to be
another. With small CFCs it should not be a problem, but once you get into
large ones with internal function calls, you're getting into dangerous
te
t;> so I thought maybe the other would work
> as well. Anyone have time to test?
>
> John
>
> -Original Message-
> From: Michael Dinowitz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 11, 2004 12:51 PM
> To: CF-Talk
> Subject: RE: Function and query name o
On Thu, 11 Nov 2004 14:33:46 -0500, Burns, John D
<[EMAIL PROTECTED]> wrote:
> Would it be possible to do ? It looks
> funny and I doubt it would work, but I know you can do name="application.getEmployees"> so I thought maybe the other would work
> as well. Anyone have time to test?
>
It won'
PM
To: CF-Talk
Subject: RE: Function and query name overwrite
Very interesting. I'd never have thought of doing a var set before the
CFQUERY. It would show up in my head as an unnecessary operation. I
think MM should add in an attribute to all tags that return data to make
the data location spe
Very interesting. I'd never have thought of doing a var set before the
CFQUERY. It would show up in my head as an unnecessary operation. I think MM
should add in an attribute to all tags that return data to make the data
location specific.
> If you scope your query as local to the function, the
Hey Mike,
If you scope your query as local to the function, the conflict will do
away. It's BP for thread safety, etc.:
Instead of:
...
Do:
...
-joe
On Thu, 11 Nov 2004 12:28:35 -0500, Michael Dinowitz
<[EMAIL PROTECTED]> wrote:
> This is not a question, just something I ran
This is not a question, just something I ran into that was interesting.
Just a small thing I ran into. I'm working with a CFC that has a function in
it called Dupe_Address. This function is called twice in a row. Inside the
function is a query of the same name. When the function is called a second
9 matches
Mail list logo
