Hi Joe,
The reason for using the duplicate() function to copy data between the request and
application scopes is that creating a pointer to an application scope query in the
request scope, i.e.
defeats the purpose of locking the application scope, since using the pointer created
in this
: RE: RE: Storing Queries in Application Scope
Hi Joe,
The reason for using the duplicate() function to copy data between the
request and application scopes is that creating a pointer to an application
scope query in the request scope, i.e.
defeats the purpose of locking the application scope
> Hi Issac,
>
> I wasnt aware you need to lock everything with poniter scoping
>method to the application. I will test this anyways. Thanks
No worries. It's a common mistake... I don't think I actually realized it
until I started turning on required checking on my development server
TECTED] [mailto:[EMAIL PROTECTED]]
> >Sent: 13 July 2002 23:56
> >To: CF-Talk
> >Subject: RE: RE: RE: Storing Queries in Application Scope
> >
> >
> >Hi Joe,
> >
> >The reason for using the duplicate() function to copy data
> >between the request and ap
> Joe
> Are you saying if i' copy a session var to the request
> scope simply using ,
> because their both complex datatypes i'm still only
> creating a pointer and actually need to use the
> duplicate function?
Actually those were my comments to Joe, but yes, using the syntax
#request.struct.va
5 matches
Mail list logo
