>
> Question on how you handle queries: Some people always include query files
> in other files, like this in actDoSomething.cfm:
> Others let the fusebox itself handle this, like this:
>

I let the fuse handle it rather than the fusebox. I have yet to hear any
good reasons, other than stylistic ones, as to why it should be handled by
the fusebox--and there seem plenty of reasons for conditional logic,
particularly complex conditional logic, that accrue when the CFINCLUDE is
handled at the fuse level.

after all, the original point for separating the queries off was to reuse
them. In the 'natural' FB1.0 way of doing things the query was just part of
the fuse. It obviously has a lot of benefits if the queries are cfinclude'd
not only for maintainability, but also readability as well as code re-use.
These points have often been made. But pushing the cfinclude up yet another
step to the fusebox doesn't seem to gain anything performance-wise and (so
far) doesn't seem to gain anything functionality wise which can't be handled
by leaving the query included by the fuse. XFA's can always handle the other
issues.  I also don't agree that the queries need to be in the fusebox in
order to 'get a picture of what the application flow is like'. I get that
fine from the fusebox with its fuses, thank you :), because i see what fuse
is called and then which fuse gets called from there. If a fuse uses or does
not use a query, why do I care (at the 'getting a picture' level)? All I
care about is flow at that point; I assume the fuse avtually works because
of course I know that I did my pre-homework with test harnasses and
Querysims.  I just like to be as far away from the database guy as often as
possible--I'd just as soon let him do whatever voodoo he does to warrant the
6 figures we have to pay him and be done with it.

I totally can understand how if you are a 1- or 2-man shop and you're also
the DB guy, how you'd cfinclude in teh fusebox rather than the fuse. But
then again, when the shop is that small, most of XFB is redundant work
anyway.

if someone could present a decent example of something that can be done with
a query included by a fusebox which also cannot be done (ro at least done as
easily) with a query included by the fuse, I'd love to hear it--for me
that's the ultimate test for which stylism to choose.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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