Yeah, I must have been getting high on some nitrous oxide floating around
the hospital, must be...

Okay, I've ground this through the test environment of science, and came up
with this...

If you name the original query "request.squid", and refer to it as
"request.squid", you can do it through CFMODULE. But duh, that's the whole
point of the request scope. Well, at least y'all know it works with query
resultsets too. I should have seen that long ago.

Can ya tell I'm neck-deep in a project and replying to this list
periodically for comic relief? Sure ya can...

> -----Original Message-----
> From: McCollough, Alan [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, May 07, 2001 3:08 PM
> To:   Fusebox
> Subject:      RE: OT: Weird request scope discovery...
> 
> Hm. I'm trying to get this to work in a test environment and it isn't
> working. BuTtTt, it -is- definately working over in an app I'm writing as
> we
> type... I bet I've got a CFINCLUDE or something invoking the query I've
> missed. Oh well, unless I prove it otherwise, chalk it up to too much
> excitement...
> 
> > -----Original Message-----
> > From:       McCollough, Alan [SMTP:[EMAIL PROTECTED]]
> > Sent:       Monday, May 07, 2001 2:59 PM
> > To: Fusebox
> > Subject:    RE: OT: Weird request scope discovery...
> > 
> > True, but I didn't have to do -anything- to the existing query to get
> the
> > results. All I had to do is CFMODULE it, and then refer to it as
> > request.(query name). I didn't have to rewrite any of the original code;
> I
> > just had to change how I tried to refer to it.
> > 
> > 
> > 
> > > -----Original Message-----
> > > From:     javier bernal [SMTP:[EMAIL PROTECTED]]
> > > Sent:     Monday, May 07, 2001 2:35 PM
> > > To:       Fusebox
> > > Subject:  Re: OT: Weird request scope discovery...
> > > 
> > > If you use a module you can return the query using
> > > <cfset caller.qry_squid = qry_squid>
> > > The recordset will be available outside the module
> > > (from the 'caller' template)
> > > Cheers
> > > javier
> > > --- "McCollough, Alan" <[EMAIL PROTECTED]> wrote:
> > > > This is a bit weird, but sorta cool, too...
> > > > 
> > > > I like putting SQL actions into a separate /SQL
> > > > directory.
> > > > Normally, I invoke these through a CFINCLUDE.
> > > > One on my SQL queries requires an attributes
> > > > variable to be set.
> > > > I tried calling this query through a CFMODULE
> > > > <CFMODULE template="/sql/qry_squid.cfm">
> > > > and then using the returned set as follows:
> > > > <CFLOOP query="qry_squid"> (I always name my queries
> > > > the same as the
> > > > filename minus .cfm)
> > > > 
> > > > Well, this didn't work.
> > > > 
> > > > BuTtTtTt...
> > > > <CFLOOP query="request.qry_squid"> works great!
> > > > 
> > > > So therefore, (attempting to sound intelligent
> > > > here...) 
> > > > IF you invoke a query via CFMODULE, the query
> > > > results are available through
> > > > the request scope as request.(query name)
> > > > 
> > > > This is pretty cool, IMHO. Quite a boon for request
> > > > scope fanatics...
> > > > 
> > > > 
> > > > Alan McCollough
> > > > Web Programmer
> > > > Allaire Certified ColdFusion Developer
> > > > Alaska Native Medical Center
> > > > 
> > > > 
> > > >
> > >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to