MIME-Version: 1.0
In-Reply-To: <DB806F2BEB98ED4FB8172F8CE09447FF946A6CD1E1@EXCH-MBX05.allegisgroup.com>
References: <DB806F2BEB98ED4FB8172F8CE09447FF946A6CD1E1@EXCH-MBX05.allegisgroup.com>
Date: Wed, 12 Dec 2012 13:10:12 -0600
Message-ID: <CAJvnOJbR58a0At--qmLDG8YBAOjWHvS3vrbUER3z3HqA0tzVxw@mail.gmail.com>
Subject: Re: OT: RE: interview question on schema design
From: Andrew Kerber <andrew.kerber@gmail.com>
To: mbrady@allegisgroup.com
Cc: "oracledbaquestions@gmail.com" <oracledbaquestions@gmail.com>, ORACLE-L <oracle-l@freelists.org>
Content-type: text/plain
Content-Transfer-Encoding: 8bit
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: andrew.kerber@gmail.com

You have expressed exactly why DBA's (in general) are so disdainful of Java
programming.  While no doubt there are exceptions, in my experience Java
programmers never look at the code underlying their objects, and blame the
DBA when their application is slow.**  In particular, Java seems very prone
to producing huge numbers of round trips from the application server to the
database and back, pulling one row or even one row and one column of data
at a time when some very simple query and schema design could get all of
the data in a single trip.
On Wed, Dec 12, 2012 at 12:33 PM, Brady, Mark <mbrady@allegisgroup.com>wrote:

> That attitude is promulgated by tools like hibernate (
> http://www.hibernate.org/) which increases the developer's ability to
> rapidly develop new applications by abstracting the database [away]. It
> abstracts the database away, so you no longer have to /think/ about it.
> Adoption of those frameworks has been slower in .net communities but where
> it is adopted you find the same attitude.
>
> <SNIP>
>
>
>


-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'


--
http://www.freelists.org/webpage/oracle-l