I have been evaluating an architecture for a system we
are building and considering the issue of optimizing
database access with entity beans.
It seems to me that entity beans are ideal in
situation where one is issuing transactions against
discrete objects in the database. Consider a system
that manages a users widgets.
If a user needs to lookup a single widget and submit
an update to that widget, the actual SQL that is
submitted to the database, a SQL SELECT and a SQL
UPDATE can, on theor own, be reasonably efficient.
However, I am concerned about situations where I need
to provide a user a list of their widgets. If each
individual widget bean issues a SQL SELECT in order to
create itself, I will have n SQL SELECT statements to
execute against the database.
Contrast this with issuing one SQL SELECT statement
that will return n rows and instantiating n objects
for each row returned. This is inherently more
efficient from the database perspective, but I am
unsure as to whether this model can be implemented in
EJB.
Any thoughts ?
//Nicholas
=====
"Suzie, Suzie, Suzie, Suzie
Suzie, Suzie Greenberg"
Suzie Greenberg, Phish
--
Nicholas Whitehead
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
