> wouldn't an object-relational mapping approach, such as hibernate,
toplink,
> etc., provide for an even greater degree of transparency, a lot less
code, and
> practically no SQL (because the SQL is auto-generated)? in addition, to
> minimize db management code even further, i would think using aspects
(e.g.,
> aspectj) to treat persistence as a cross-cutting concern would further
> reduce the amount of code to be written, simplify that which does have
to be
> written, and centralize all the persistence code so that it's easier to
manage
> and guaranteed to be applied consistently.
ORMs such as toplink and hibernate suffice only for simple projects.
Complicated issues such as security, caching, clustering, partitioning
and others make them inconvenient for complex projects. The more
control you have on your data the better. As for SQL, sometimes to
write SQL is simpler then HQL.
|
