ROSSEL Olivier wrote:
O/R is not always needed. Sometimes you just want to work with a relational master/detail (ie, next row(); next row();).

My concern is not to have to think in term of (for example) Primary Key/Foreign Key or Conposite Key...
Sometimes the business requirements are that you have a master detail ( a 2 dimensional array in O/R), or a many to many.
RowSet.next() can be easily overridden.
Relational algebra can explain some business easily, that O/R can't.

In general, to write a good db application, one needs to know the db.
.V


This is too much low level for me. And some programmers I talk
to really don't care about my DB model.
That's why I am looking for tools that provide an abstract layer between
DB and business objects worlds.

I think O/R is exactly that. I don't see exactly what JDO is. An API by Sun for those kind of
problems?

This e-mail is intended only for the above addressee. It may contain
privileged information. If you are not the addressee you must not copy,
distribute, disclose or use any of the information in it. If you have
received it in error please delete it and immediately notify the sender.
Security Notice: all e-mail, sent to or from this address, may be
accessed by someone other than the recipient, for system management and
security reasons. This access is controlled under Regulation of
Investigatory Powers Act 2000, Lawful Business Practises.



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to