Yep. If I say "UPDATE foo SET squid =
`#PreserveSingleQuotes(attributes.squid)#`", it fails. I don't know why, but
if I do the PSQ first, then it works fine. I tried it just the other day cuz
I looked at some old code and said to myself "Why am I doing this?" Then I
remembered why. And this is with CF 4.0.1, and 4.5... Who knows?
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Dustin Breese [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, August 28, 2000 8:29 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Request scope (RE: No more need for cflock!!)
>
> Alan,
>
> I use PreserveSingleQuotes() all the time in my queries -- do you get an
> error when doing so?
>
> Thanks,
> Dustin
>
> -----Original Message-----
> From: McCollough, Alan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 28, 2000 10:14 AM
> 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.
------------------------------------------------------------------------------
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.