Consider the following situation:
A complex query that is broken down to mutiple queries that require at least
one temporary table. If these queries are called from a SP then the
temporary table(s) exist only for the duration of that SP.
The other way of course is to drop the temp table(s) at the end of the
mutliple queries.
Just a thought.
Keith
> > move into the database, the better - that cf is best used for
> > outputting/formatting but that the processor-intensive stuff
> (loops, etc)
> > should be moved to the db when possible. What's the rational for saying
> that
> > you shouldn't?
>
> i didn't say "not in the database", i said "not in an sp". and the loops
> here were loops building dynamic sql code. cf builds the sql, the
> backend executes it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
