> Hm.... Okay. I see what you're saying, Paul. Is there a preferred way to
do
> dynamic sql in the database? Or, is the idea that one is better off doing
> that which is dynamic in cf?
if security/management is a concern, sp are good containers for a
lot of stuff. centralized, secure, transparent, etc. these are plenty
valid reasons for using sp, especially with sql server 7 & sp_executesql
which does buy you some optimization & caching. if speed is important,
the trick is to try *not* to use dynamic sql. if you have 3 cases, build 3
sp & have cf decide which one to call (or a container sp which would
decide which sp to EXEC). we often go to "ridiculous" lengths to get
static sql sp. if we can't we'll build the sql in cf if security/management
not an issue.
> (Just trying to learn more about enterprise database solutions - not
> challenging your viewpoint.)
challenge away, i'm by no means an expert. just have some strongly
held opinions based on what passes for experience in my neck of
the woods.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
