> procedures and i apologize, but what is the point or what
> is the benefit rather?
> from what i have read so far i havent seen a point, but
> maybe i just dont understand the concept completely. whats
> hard about saying <cfquery.../> <cfquery... /> ... if 1
> query sets off another, why not just write it out??
> maybe im missing the concept like i said, so if anyone has
> an example they wish to share please enlighten me.
> thanks.
> joe
Asside from the mentioned performance improvement (execution plans are
pre-compiled and stored), stored procedures also provide "better
encapsulation". In other words, if you write it out and then later
discover that you need the same set of queries on several pages, you
have to decide how to reuse those queries, from the worse (cut and
paste) to the best alternatives (custom tag, function or cfc method
and/or stored procedure -- I prefer to use a custom tag and/or
function that automates the stored procedure, saves me lots and lots
of keystrokes in the CF template). And then there's also the fact that
stored procedures are immune to SQL injection attacks. DBA's like them
in some environments where the DBA is separate from the CF scripting
department (not often in my experience) because they let the DBA
maintain strict control over data access -- which can also go back to
that issue of better encapsulation if the CF scripts aren't the only
point of access to the database - the stored procedures can be reused
by multiple applications which might access that database (cf scripts,
client-server apps, etc - this can be important in enterprise
environments where the database is shared amongst many departments).
s. isaac dealey 954.927.5117
new epoch : isn't it time for a change?
add features without fixtures with
the onTap open source framework
http://www.sys-con.com/story/?storyid=44477&DE=1
http://www.sys-con.com/story/?storyid=45569&DE=1
http://www.fusiontap.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
