RE: DBA Hacks Book
- From: "rob zijlstra" <rmsah@xxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 21 Jun 2004 08:41:19 +0200
Darrell, sorry if the tone of the message offended you. Was certainly not
the intention. For the rest, I could answer your points, but I think it
would be pointless to start a discussion here that is rather OT.
Greetings,
Rob Zijlstra
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Darrell Landrum
Sent: zondag 20 juni 2004 04:27
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: DBA Hacks Book
DBA Hacks BookWell, Rob, that's a nice Mr. holier than thou attitude you
have there. In reference to the note at hand you don't know what you're
talking about.
I didn't say users, I said developers and guess who developed said database,
although the database is not the problem. I'm talking about high paid
programmers with at least several years and several classes behind them.
These people frequently do the wrong thing, often against advise and even
against established standards (could go all night on the points of failure
in an organization that let that happen). Then, it is not just the
programmer, but the DBA as well who gets paged in the middle of the night
when their production job runs long and I find a pl/sql loop which calls the
same function to get a fiscal month close date to compare to each of
64,000,000 records, 64,000,000 times rather than once at the beginning of
the program. This occurred some months after the reviewing DBA on the
project had given them specific details on how to code this better.
So, here we go again, indeed. It is not me, but you who is short sighted in
this case, and I do have just cause for complaining.
----- Original Message -----
From: rob zijlstra
To: oracle-l@xxxxxxxxxxxxx
Sent: Friday, June 18, 2004 8:40 AM
Subject: RE: DBA Hacks Book
>> I work with developers who use our databases all the time in ways that
aren't anticipated but I can't discuss it without a lot of unfriendly
language.
Here we go again.
In prehistoric times (about 1980) when I started to learn to program, one
of the first things I learned that if a user does something that you hadn't
anticipate, it was not the fault of the user. Of course it only meant that
the programmer didn't use his brains enough to foresee these things. He
should make a better program, and certainly NOT try to explain to the user
that 'he shouldn't do that and that'; no, if he was a real programmer, the
user could NEVER even do 'that and that'.
The sentence above only means to me, that the person who developed the db
in question should try to work smarter instead of complaining!
Greetings,
Rob Zijlstra.
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
