Is this the commonly used method for caching queries?
Do ya'll prefer to name them with the application
scope or use the cachewithin attribute? If you use
the application scope method, I've written a custom
tag which may be of use. It allows you to write your
queries without a scoped name (by duplicating it to
the application scope).. and duplicates them to
whatever scope (and name, if necessary) you want. I'm
kind of thinking using the request scope for the
outputted query is a bad idea.. maybe stick to the
variables scope for that. This same custom tag also
works for structures.
It takes care of the locking, and in the case of a
query probably reduces the time of the exclusive lock.
I haven't distributed this tag b/c I
figured I'd mostly wasted time creating it b/c the
cachewithin method of caching was easier. Lemme know
what ya'll think.
tag attached.
-----Original Message-----
From: Marsh, Jeffrey B [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 15, 2000 12:17 PM
To: Fusebox
Subject: RE: the dot notation
You should scope one query to the application scope
and use it
where needed.
Each circuit is not really dependent upon anything
from any
other circuit.
Each circuit is using information available to any
template in the
application.
Hey notice I'm spelling "circuit" correctly now? :-)
---
Jeffrey B. Marsh
professionals built the Titanic
amateurs built the Ark
-----Original Message-----
From: Nat Papovich [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 14, 2000 5:54 PM
To: Fusebox
Subject: RE: the dot notation
It must have been all that work on the book - the book
that
Craig and Hal
claimed all the credit for. Yeah, that's it. If Hal
and Jeff P
are coming up
with such good ideas, they must not be working hard!
I second the notion that FB should steer in the
direction of cfinluding
indexes. There are a few more questions I have though,
like sharing code
amongst circuits. What happens if I have an
application-wide query like:
SELECT * FROM STATES
and I want to scope the query to
application.stateslist and
then scope that
to request.stateslist. Does every single circuit app
need this
thing? What
if Jeff calls his circuit's query "request.listStates"
and Hal calls his
"request.StatesList", and then Noam makes a stored
procedure that really
speeds up that query and names his
"request.StatesQuery". Now,
you have 3
separate piles of memory taken up, when only one would
do. What's the
convention for sharing stuff across circuits? Each
circuit is
not supposed
to rely on anything else from any "wrapper" circuits,
but in the case
mentioned above, you really should break the rules for
a massive
time-savings.
NAT
> -----Original Message-----
> From: Steve Nelson [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 14, 2000 3:58 PM
> To: Fusebox
> Subject: Re: the dot notation
>
>
> JEBUS save me!
>
> Nat.... why are we such lunkheads?!
>
> btw, for anyone that cares.... I just finished a
pretty slick tool for
> importing data from my backend database into
Microsoft Money
> (accounting
> package). I'm pretty sure the same thing could work
with
> Quicken and/or
> Quickbooks.
>
> Steve Nelson
> http://www.SecretAgents.com
> Tools for Fusebox Developers
> (804) 825-6093
>
> Hal Helms wrote:
> >
> > Ah, yes, I've got it now! Just a little slow on
the upbeat...
> >
> > Anyway, if you place this in your myGloblals.cfm
file, then
> #images# will
> > point to a directory called images below the
nested fusebox:
> >
> > <cfset images = "#GetDirectoryFromPath(
> GetCurrentTemplatePath() )#images\">
> >
> > Hal Helms
> > == See www.ColdFusionTraining.com
> <http://www.ColdFusionTraining.com> for
> > info on "Best Practices with ColdFusion & Fusebox"
> training, Jan 22-25 ==
=====
Ken Beard, Senior Developer
Stampede Network
Tampa, FL
(813)622-7655 ext.246
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
