Whoa, not so fast - 
Scopes are also available as structures, but the main issue is Visibility -
that is from what CFM templates can you access the variables - check the
online help it gives a decent coverage of it.

What you're doing is just creating a structure variable inside the variables
scope: Variables.Sql.Squid 

HTH,
Noam

        ----------
        From:  McCollough, Alan [SMTP:[EMAIL PROTECTED]]
        Sent:  Monday, 28 August 2000 18:14
        To:  '[EMAIL PROTECTED]'
        Subject:  RE: Request scope (RE: No more need for cflock!!)

        I'm gonna toss in my quick two cents here.

        It appears to me that "scope" in CF is purely arbitrary, and in
fact, is
        just a different way of representing a structure. It occured to me
the other
        day that I can create any darn scope I want.

        For example, I, as a habit (bad or good you decide) take any
variable that's
        gonna be saved as text into SQL, and PReserveSingleQuotes on it.
I've also
        noted that you cannot directly say, in the midst of a CFQUERY,
"INSERT
        '#PreserveSingleQuotes(squid)#'"' you gotta do the PSQ first.

        SoOo, what I do is, if I have a var squid, I'll say "CFSET sql.squid
=
        PReserveSingleQuotes(squid)", thus, creating a new variable, which
I've
        scoped as "sql." I note that you can use any darn name you like, so
long as
        it isn't already a predefined CF scope.

        I think that behind the scenes, any variable is being implicitly
scoped
        anyway, and in fact, is being stored as a structure. Its just a
theory, but
        I think its right...

        Alan McCollough
        Web Programmer
        Allaire Certified ColdFusion Developer
        Alaska Native Medical Center

        > -----Original Message-----
        > From: Marcuse Franca [SMTP:[EMAIL PROTECTED]]
        > Sent: Saturday, August 26, 2000 3:32 PM
        > To:   [EMAIL PROTECTED]
        > Subject:      RES: Request scope (RE: No more need for cflock!!)
        > 
        > 
        > An example would help, I guess...
        > 
        > -----Mensagem original-----
        > De: Nat Papovich [mailto:[EMAIL PROTECTED]]
        > Enviada em: 26 Agosto, 2000 19:59
        > Para: '[EMAIL PROTECTED]'
        > Assunto: RE: Request scope (RE: No more need for cflock!!)
        > 
        > 
        > >From the Studio-based Help:
        > 
        > Request scope -- a reserved variable/scope allows for the
convenient
        > storage
        > of data that pertains to the processing of a single page request.
It is a
        > structure named "request". The variable is available in all
templates:
        > base,
        > includes, and custom tags.
        > 
        > Schweet, huh?
        > 
        > Nat Papovich
        > ICQ 32676414
        > "Whatever you do may seem insignificant,
        > but it is most important that you do it." -M. Gandhi
        > 
        > 
        > -----Original Message-----
        > From: stas [mailto:[EMAIL PROTECTED]]
        > Sent: Saturday, August 26, 2000 3:53 PM
        > To: [EMAIL PROTECTED]
        > Subject: Request scope (RE: No more need for cflock!!)
        > 
        > 
        > Could anybody please give a crash course on the request scope? It
is not
        > covered at all in the first Forta book. Thanks!
        > 
        > 
        > -----Original Message-----
        > From: Hal Helms [mailto:[EMAIL PROTECTED]]
        > Sent: Saturday, August 26, 2000 3:25 PM
        > To: [EMAIL PROTECTED]
        > Subject: RE: No more need for cflock!!
        > 
        > 
        > Very cool, Fusedude(tm). I recently changed all our application
vars to
        > request vars for a BIG app, and it worked bee-yoo-tifully.
        > 
        > The only change I'd make to your fusedoc is that you only need the
double
        > pipes || to distinguish different sections of the docs.
        > 
        >
--------------------------------------------------------------------------
        > --
        > --
        > To Unsubscribe visit
        >
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
        > send a message to [EMAIL PROTECTED] with
'unsubscribe' in
        > the body.
        >
--------------------------------------------------------------------------
        > --
        > --
        > To Unsubscribe visit
        >
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
        > send a message to [EMAIL PROTECTED] with
'unsubscribe' in
        > the body.
        > 
        >
--------------------------------------------------------------------------
        > ----
        > To Unsubscribe visit
        >
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
        > send a message to [EMAIL PROTECTED] with
'unsubscribe' in
        > the body.
        
----------------------------------------------------------------------------
--
        To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to