RE: JAVA Developer
- From: <Joel.Patterson@xxxxxxxxxxx>
- To: <Andrew.Kerber@xxxxxxx>, <oracledba.williams@xxxxxxxxx>
- Date: Mon, 8 Jan 2007 14:57:22 -0500
Yes, my first impression is how you develop java classes before knowing
what the schema looks like, but I'm the neophyte for these purposes.
I got one response as follows: Any elaborations? Someone touch on
hibernate, (and toplink) again or me.
"2 basic areas of potential conflict are how the object domain model is
managed relative to physical database design, and the other is result
set persistence relative to transaction concurrency.
Many java architects/developers believe that the object model should
translate directly to the physical DB model. If you as the DBA allow
that, your database manageability, including performance, is doomed.
When you perform physical design, you'll be breaking some of their
object classes, which can potentiall cause a ton of angst. In order to
gain decent performance, you'll have to stick to your design guns, and
if the JAVA person doesn't understand how the handoff works between
object modeling and database modeling, there may be a lot of arguing.
Persistence is another hot button. If they believe in using a third
party persistence engine, such as a Hibernate, this can lend itself to a
lot of ambiguity between what the overall database transaction mix is
doing on disk and what the result set that the persistence engine is
managing for the long-running transaction that may want to execute
updates/deletes based on what it sees. Content management can become
problematic if the applications is not coded properly, and these can
quickly become YOUR problem if you're not diligent during development."
Joel Patterson
Database Administrator
joel.patterson@xxxxxxxxxxx
x72546
904 727-2546
________________________________
From: Kerber, Andrew [mailto:Andrew.Kerber@xxxxxxx]
Sent: Monday, January 08, 2007 2:19 PM
To: oracledba.williams@xxxxxxxxx; Patterson, Joel
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: JAVA Developer
I would love to hear the answer that you expect to hear for that, since
the answer I would give is the Java classes would be derived from the
data model.
Andrew W. Kerber
Oracle DBA
UMB
"If at first you dont succeed, dont take up skydiving"
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Dennis Williams
Sent: Monday, January 08, 2007 1:12 PM
To: Joel.Patterson@xxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: JAVA Developer
Joel,
My question would be "Do you feel data modeling should be done
separately, or should the data model be derived from the Java classes?"
Dennis Williams
------------------------------------------------------------------------
------
NOTICE: This electronic mail message and any attached files are
confidential. The information is exclusively for the use of the
individual or entity intended as the recipient. If you are not the
intended recipient, any use, copying, printing, reviewing, retention,
disclosure, distribution or forwarding of the message or any attached
file is not authorized and is strictly prohibited. If you have received
this electronic mail message in error, please advise the sender by reply
electronic mail immediately and permanently delete the original
transmission, any attachments and any copies of this message from your
computer system. Thank you.
========================================================================
======
Other related posts:
