> 1. They execute faster. The db (I only know from Oracle and SQL
> Server, if
> others are different it doesn't really concern me) can optimize the
> execution plan.
>
Prepared statements execute at the same speed as stored procedures.
> 2. You can often times do more. There are things I can do in a pl/sql
> package/procedure that I cannot do in a query call
>
For example?
> 3. You can limit access with them. Now granted you can set it up so
> you are
> only selecting from a view in your query block as well, but it makes
> more
> sense to me to do it in a procedure.
>
Why does it make more sense?
> 4. An additional layer of security. You can ensure that you user not
> only
> cannot execute the procedure, but they can't even tell it exists.
>
If the user is executing the procedure how could they not know it
exists?
> I am sure there are more reasons, but I think those are sufficient to
> use
> procedures.
>
If that's all, I guess I'll continue to use cfquery.
-Matt
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
- why are procedures better? (was: RE: Securing CF Apps.) Heald, Tim
- Re: why are procedures better? (was: RE: Securing C... Jochem van Dieten
- RE: why are procedures better? (was: RE: Securing C... Matt Liotta
- RE: why are procedures better? (was: RE: Securi... Tom Kitta
- RE: why are procedures better? (was: RE: Securi... Tony Weeg
- Re: why are procedures better? (was: RE: Se... Deanna Schneider
- RE: why are procedures better? (was: RE... Tony Weeg
- Re: why are procedures better? (was: RE... Matt Liotta
- RE: why are procedures better? (was: RE... Greg Luce
- Re: why are procedures better? (wa... Deanna Schneider
- RE: why are procedures better? (was: RE: Securi... Steve Nelson
- RE: why are procedures better? (was: RE: Securing C... Jochem van Dieten
- RE: why are procedures better? (was: RE: Securi... Steve Nelson