Re: "We don't do triggers"

some take this stand for portability -- stored procedures must be written, at least partially, in a proprietary language that is not portable across databases

so what's the target deployment environment(s)?

--mcs

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:3fbe0e38$0$9392$ed9e5944_at_reading.news.pipex.net...
| "(Pete Cresswell)" <x_at_y.z> wrote in message
| news:q9lqrv4rdlcughil17flbbu2ln162bbu7r_at_4ax.com...
| > I'm on the periphery of a rather large (to me, at least: $10 mil..)
| project in
| > which the tech folks flatly say "NO STORED PROCEDURES: NONE, NOT EVER!".
| >
| > There's got to be a reason, but I don't know enough to even guess at it.
| >
| > Somebody?
| I'd ask. If the answer is all the logic etc belongs in the application
| explain that there will be 2 corollaries
|
| 1. NO DATA LOADS EVER. Key it through the app ALWAYS. even 10 million
rows.
| 2. NO INTERFACES TO OTHER SYSTEMS, EVER. make other systems talk to the
app.
|
| They both follow logically from this 'design' rule.
|
|
| --
| Niall Litchfield
| Oracle DBA
| Audit Commission UK
|
|
Received on Fri Nov 21 2003 - 09:22:53 CST