<snip>
> data directly, no diamond can form. Now, if we prevent stove
> piped access
> to the data store, I can see no reason for O:R mappings, as
> the only access
> path to the data would be via the entities. If there is no
> O:R mapping then
> we can indeed store the entity in an opaque fashion, again as
> no one can get
> to the data except via the entities. Now if this is so, why
> use an RDBMS
> anyways, why not use an object database? Or, does a well
> designed in-memory
> entity bean implementation replace the OODBMS?
>
> These basic questions still haunt the direction of EJB and
> unless managed
> will lead to more issues like Jay originally posted.
>
> Dave Wolf
> Internet Applications Division
> Sybase
>
the problem is, that normally the decision which database to use, is not
made by the developer, but by the customer, who mostly already has a
database and does not want a second one. That's why we will still have to
deal with RDBMS in the future (unfortunately).
Ulf Gohde
CEYONIQ
===========================================================================
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".
