Two examples from my own experience:
A few years ago when I was starting out, I got involved on a database
project where all the constraints were coded rather than declared at
database level (it wasn't Oracle, but the principle remains the same). It
was a relatively small project and the guy
Thanks for all your comments (especially the ones that made me laugh).
Now at least I have some input from experienced people to put before my
boss.
Craig
-Original Message-
From: Craig Healey
Sent: 23 October 2002 18:45
To: Multiple recipients of list ORACLE-L
Subject: Theory v
As this topic just hits my hot button, I'm going to chime in my 2 cents
worth in as well. This in spite of the fact that you have already gotten
some great responses.
I come from an environment where we have distributed data all over creation.
IMS, DB2, Oracle, you name it we have it popping up
To me this comes under the heading of common sense.
My $0.02 worth,
Ken Janusz, CPIM
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Thursday, October 24, 2002 9:33 AM
As this topic just hits my hot button, I'm going to chime in my 2 cents
worth
The developers working on our new VB app are also responsible for
setting up the Oracle DB behind it. The app is for an order
entry/despatch/warehouse system with 5 million customers and 1000
orders per day. We have nearly 400 tables. They are not planning on
using primary keys/secondary keys, as
Craig,
No, this is not normal. They have purchased a Caddy so they can push their
grandma to the beauty parlor to get her blue-hair done - they will never
start the car.
Why in the hell did they purchase Oracle in the first place? Talk about a
waste of money!
If you cannot stop them now, then
Craig, i dont know jack about VB but M$ Access wont let you do
updates(according to my sources) unless there is PK or Unique index on
the tables.
joe
Craig Healey wrote:
The developers working on our new VB app are also responsible for
setting up the Oracle DB behind it. The app is for an
Craig,
Unfortuneatly this happens alot. Many developers have an over inflated view of their abilities and think they can write their code good enough to handle this. Every time I have seen this in place I have seen data integrity problems. Some major application vendors do this to provide the
it's not common and you should insist on primary and foreign key
constraints.
all you need is ONE user to hack into the database outside the app and
insert/delete/update rows that violate the integrity constraints and
your app stops working.
--- Craig Healey [EMAIL PROTECTED] wrote:
The
When code is developed to be database generic, developers will steer away from
code for a specific database. However, foreign key and check constraints hardly fall
into this category. I don't use Sqlserver or DB2, but I would guess that they
implement FKs and constraints. Your developers
Craig - I've seen large/busy databases run with RI handled outside the db.
Most common with package apps like Peoplesoft. They do that because they
want to run on many DBMSs and each handles RI differently. To reduce
development cost, they code once to the least common denominator. Thus no
RI
Wow, Life is stranger than fiction!
First of all buy stock in your hardware vendors since every query will
result in a table scan of every table and if you get more than an
intermittant workload on the system, it may very well come down onto its
knee's. indeed they are making it a very expensive
This is VERY wrong.
I know they are perfect, but one bug in the code will cause data loss,
order entries without a correct customer code etc.
Lets say that a year from now one customer complain.
They print a report and see that two entries are missing.
You check for orders with incorrect
recipients of list ORACLE-L
Subject:Re: Theory v Practice
When code is developed to be database generic, developers will steer
away from code for a specific database. However, foreign key and check
constraints hardly fall into this category. I don't use Sqlserver or DB2,
but I would
: Wednesday, October 23, 2002 2:39 PM
To: Multiple recipients of list ORACLE-L
Subject:Re: Theory v Practice
it's not common and you should insist on primary and foreign key
constraints.
all you need is ONE user to hack into the database outside the app and
insert/delete/update rows
To: Multiple recipients of list ORACLE-L
Subject: Theory v Practice
The developers working on our new VB app are also responsible for
setting up the Oracle DB behind it. The app is for an order
entry/despatch/warehouse system with 5 million customers and 1000
orders per day. We have nearly 400
: Craig Healey [mailto:C.Healey;hhsuk.com]
Sent: Wednesday, October 23, 2002 10:45 AM
To: Multiple recipients of list ORACLE-L
Subject: Theory v Practice
The developers working on our new VB app are also responsible for
setting up the Oracle DB behind it. The app is for an order
entry
Subject: Re: Theory v Practice
it's not common and you should insist on primary and foreign key
constraints.
all you need is ONE user to hack into the database outside the app
and
insert/delete/update rows that violate the integrity constraints and
your app stops working
, 2002 1:45 PM
To: Multiple recipients of list ORACLE-L
Subject: Theory v Practice
The developers working on our new VB app are also responsible for
setting up the Oracle DB behind it. The app is for an order
entry/despatch/warehouse system with 5 million customers and 1000
orders per day
that they wear clothing in bright colors.
-Original Message-
From: Craig Healey [mailto:C.Healey;hhsuk.com]
Sent: Wednesday, October 23, 2002 1:45 PM
To: Multiple recipients of list ORACLE-L
Subject: Theory v Practice
The developers working on our new VB app are also responsible for
setting
On Wed, 23 Oct 2002, Mandar A. Ghosalkar wrote:
3 yrs after ur developers code the VB app, the original team vanishes(they start
working on .net .. or maybe java)
The new team even after going through the docs and vb application libraries, forget
the right joins and insert invalid
These developers are wrong, and the problem is far worse than primary /
foreign keys. The fact that your developers would say this indicates they
have no knowledge of even the most basic Oracle fundamentals, so they will
be making other serious mistakes too. If you have even an ounce of personal
for you.
Make sure that they wear clothing in bright colors.
-Original Message-
From: Craig Healey [mailto:C.Healey;hhsuk.com]
Sent: Wednesday, October 23, 2002 1:45 PM
To: Multiple recipients of list ORACLE-L
Subject: Theory v Practice
The developers working on our new VB
C.Healey@hhsu To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
k.com cc:
Sent by: Subject: Theory v
24 matches
Mail list logo
