Re: "We don't do triggers"

"Peter Connolly" <peter_at_alum.wpi.edu> wrote in message news:39fde041.0311242103.4017e449_at_posting.google.com...
> Daniel Morgan <damorgan_at_x.washington.edu> wrote in message
news:<1069449434.96746_at_yasure>...
> > Comments in-line.
> >
> > Peter Connolly wrote:
> >
> > > In addition to portability, another reason for specifying no stored
> > > procedures could be to ensure that there is no business logic in the
> > > database procs.
> >
> > Because you value data corruption?
>
> Are you saying that pl/sql developers are better than java developers?
> There is no reason to believe that using pl/sql or triggers is any
> more effective than java in terms of data corruption. Last time I
> checked, pl/sql still couldn't use full regular expressions to
> validate data. Regardless of how it is implemented, a developer must
> code it. I've seen just as many bad pl/sql developers as java
> developers. What it really comes down to is: which is the better way
> to implement it, in a J2EE server or Pl/SQL.

No. He is saying that Enterprise systems and data stores have dataloads/other systems interfaces etc. The best place to ensure data integrity is as close to the data as possible.

> Advantages to J2EE:
> Portable

What is the advantage of this for the *client* customer. How often do they change architectures?
> Object-oriented
> Vendor independent

So what.

> Flexible (can talk to almost *any* other system: LDAP, doc
> repositories, etc)
> Can provide data in any format (http, web-service, xml)
as can pl/sql

> ...
>
> Advantages to PL/SQL:
>
> Better performance
> May be quicker to implement as SQL is a 4GL.
> Can talk to any other Oracle system (that your dba controls)
Can't be circumvented,made obsolete when something else needs to access your data.

<snip>

> Stored procedures are not flexible at all, they are not
> object-oriented and they have very limited ability to talk to other
> systems (can pl/sql call a web-service to get information?).

take a look at java stored procedures and external procedure calls.

-- 
Niall Litchfield
Oracle DBA
Audit Commission UK