to write packages and procedures for you to call. They can then do cross
tabs, array loops and all sorts of other things that you can't do in a
regular query block, such as work with the oracle session, db user accounts,
security according to db roles - which doesn't work with a query block.
--
Timothy Heald
Web Portfolio Manager
Overseas Security Advisory Council
U.S. Department of State
571.345.2319
The opinions expressed here do not necessarily reflect those of the U.S.
Department of State or any affiliated organization(s). Nor have these
opinions been approved or sanctioned by these organizations. This e-mail is
unclassified based on the definitions in E.O. 12958.
-----Original Message-----
From: Tangorre, Michael [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 9:37 AM
To: CF-Talk
Subject: RE: why are procedures better? (was: RE: Securing CF Apps.)
> I certainly understand your position. But what does that have
> to do with comparing stored procedures to queries? It may
> matter in your particular situation, but we are supposed to
> be having a generic technical debate.
Yes, we are having a generic technical debate, and what I am saying is that
when the team setup or hierarchical setup is not ideal, separating work out
makes the project move along faster. Stored procs come into play here in
that someone can tackle this aspect while other things are being taken care
of.... That's pretty generic... Just another situation in which stored procs
are better.
Mike
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
