Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
Date: 2 Jun 2006 10:46:39 -0700
> We are both discussing layered architectures, and we both
> posit a layer "closest" to the database. (We usually call this
> a "lower" layer, with the metaphor being that the dbms is
> at the bottom, even though an rdbms is using a higher level
> of abstraction.)
> This layer is part of the application. It is an important part;
> perhaps the most important part. It should not, indeed cannot,
> be isolated from SQL. This does not imply that SQL will
> be present at *every* layer of the code. If you find you
> are generating HTML and invoking JDBC in the same class,
> you might have a problem with the modularization of your
> code, ha ha.
I think it would be outstanding to have relations as first-class entities in any language. It would be terrific to implement much GUI, XML, and other functionality in terms of relations (even purely in-memory ones, either for app purposes or as "projections" of the relations in the RDBMS). The code would be shorter and better, and relations could also be an effective interface to many outside services (as a simple example: HTTP defines verbs like GET, POST, DELETE, and some others with a distinctly simplistic CRUD flavor, and the defining RFCs suggest (mostly unimplemented) ACID semantics).