Isolatable Concerns (was: Transaction Oriented Architecture...)

I think the ideal is "isolatable concerns", not "separated" concerns.
In relational thinking, what is together or apart is considered a
specific viewpoint. Navigational (OO and file) thinking tends to view
things as physical lumps that are either together or not together
because a physical lump cannot be in two places at once.

However, relational *does* allow something to be two "places" at once;
it transcends physical relationships and 3D space. As long as the
attributes or relationships are there to *identify* different aspects,
different aspects can be searched, sorted, or presented however the
h3ll one pleases. I am not stuck with Bill Gate's physical grouping or
Scott McNeally's.

Thus, if you "mark off" where SQL is to make it easier to find and
change, you could potentially group and edit all SQL together on your
screen if needed. (Or perhaps all SQL matching keywords sought.)

The problem is that OOP and files don't easily supply this point of
view. In the future hopefully code will be managed in RDBMS at a
function/method granularity, if not smaller, instead of hierarchical
directories and files at a module level.

But first Pinky and I have to convince the world that tables are
better....

-T-
Johny Appleseed was a "troll" too.

.