"karthik" <anon@anon.com> wrote in message
news:bdln6h$7hk$1@mozo.cc.purdue.edu...
> That, i would blame it on the guy who does and not on the ERP vendor.

That would be your customer. You know the person who owns the data and is
paying the ERP company big bucks for one view of it. Placing RI only in the
app in my view is purely done to make it easier for the software vendor and
harder for the people whose businesses this stuff is supposed to make easier
to run.

> From experience, even having stored procedures/triggers must be avoided
> as much as possible if performance is not an issue (as in several master
> data screens). Imagine having to change 4-5 stored procedure programs
> and having to test them for each database for every line of changed code.!

Imagine having to test each changed line of code against every platform you
support, my god you might slow the release cycle down and produce quality
product. One could go further and test against customers data as well.


--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************

Sybrand Bakker <gooiditweg@sybrandb.demon.nl> wrote in message news:<kr9pfv8kb2pecgmgtjvrd7gafcukljh3jt@4ax.com>. ..
> On Fri, 27 Jun 2003 13:15:40 -0700, "Mikito Harakiri"
cut
> That's also my impression. And of course, people using Oracle Apps are
> still forced to run Oracle 8.1.6 server *and* Oracle 8.0.6 client.
> Oracle Apps, from the technical view, is just a big mess, and the
> worst product they ever sold.
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address

Forced to use 8.1.6 and client 8.0.6? Not so.

gforestieri9@yahoo.com (Greg Forestieri) wrote in
news:6a8cdd95.0306300419.2e8e37bf@posting.google.c om:

> This is the reason I cringe when I hear about apps people trying to
> make their apps DB-neutral. It's not technically feasible, at least
> not safely.

This is the whole Java mentality too: app is DB-neutral. What they
end up is mediocrity across all vendors.
--
Pablo Sanchez, Blueoak Database Engineering
http://www.blueoakdb.com

gforestieri9@yahoo.com (Greg Forestieri) wrote in message news:<6a8cdd95.0306300419.2e8e37bf@posting.google. com>...
> karthik <anon@anon.com> wrote in message news:<bdln6h$7hk$1@mozo.cc.purdue.edu>...
> >
> > Front end logic (like in VB, Oracle Forms and Centura) is much more
> > easier to maintain. Its suboptimal as its slower. But where performance
> > is not an issue, one is better of putting the logic in the front end
> > if we are connecting to 3-4 databases.
> >
>
> I disagree.
>
> 1) Oracle Apps had *more* foreign keys 6 years ago. They were pulled
> out to "*improve performance*". The enforcement of the rules that
> were pulled is now done in the forms. It's faster - but at a price of
> less back end integrity and knowing that every time Mr. User plugs
> into his DB he can throw the DBAs into a fit by invalidating the data
> with the click of a mouse.
>
> 2) It's *much* easier to enforce these rules in the database. That's
> a large part of the reason we use relational DBs instead of using
> nekkid b+tree or ISAM data systems.
>
> I agree that if you are going to connect to 3 or 4 different relation
> DB vendors you are better off with a separate enforcement mechanism.
> But being able to connect to all those DBs disables the part of the DB
> that is at times most useful. That which helps keep it healthy and
> correct.
>
> Greg
>
>
> This is the reason I cringe when I hear about apps people trying to
> make their apps DB-neutral. It's not technically feasible, at least
> not safely.

Yes, it is enough to make one cringe. As to its feasibility, I work
on them all the time and have for decades! Give me a macho
smiley-face pin while I tightrope walk on razorblades! I tried to be
Oracle specific, really, I did...

jg
--
@home.com is bogus.
And what about Rdb?

Sybrand Bakker <gooiditweg@sybrandb.demon.nl> wrote in message news:<fvqsfvo5148m8k40pj8q1dhimrs2ho4udq@4ax.com>. ..
> On Sat, 28 Jun 2003 22:52:29 -0500, karthik <anon@anon.com> wrote:
>
> >Front end logic (like in VB, Oracle Forms and Centura) is much more
> >easier to maintain. Its suboptimal as its slower. But where performance
> > is not an issue, one is better of putting the logic in the front end
> >if we are connecting to 3-4 databases.
>
> I disagree it is easier to maintain. Usually it is spread all over the
> application. Usually the unlucky third-party DBA doesn't have access
> to the source/ Usually performance *is* an issue, and the application
> guys are blaming the third-party DBA for it all the time.

Ya got that right! It may be easier to maintain for a particular
problem, but overall it has additional problems not seen in
centralized logic. The tradeoff generally strongly favors
centralization, especially since that makes it easy to undo when
necessary. As to performance... the more specificity you have, the
more performance you get. How many dollars per hour do you want to
go?

> Usually NO ONE is EVER connecting to 3-4 databases, and NO ONE is so
> STUPID to use databases from different vendors.

Sybrand! You really are underestimating people's stupidity! :-)

> Usually those ERP applications are just a BIG PAIN IN THE ASS

True, that's why we all _should_ have job security, barring complete
civilization breakdown.

jg
--
@home.com is bogus.
But it never works out logically.