Re: Isolatable Concerns

topmind wrote:
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;
Relational, structured, OO, and other methodologies all allow for abuses to take place. For 99.999% of items I'll stick with things should be recorded once and only once. Everything else is redundant.

Why sprinkle SQL around, especially if its redundant? That coding style shows no appreciation for the lessons learned designing relational databases (unless those, too, were rife with redundancy)

I thought of another reason overnight not to sprinkle SQL around -- performance. I can tune a procedure and everyone using it benefits. How can I make sure everyone's SQL is efficient? If table statistics change and old SQL sucks wind, am I go to hunting for it? No, I think the value the burying or generating SQL hither and yon throughout an application is sufficiently discredited.

--
Visit <http://blogs.instreamfinancial.com/anything.php> to read my rants on technology and the finance industry.
.

Relevant Pages

  • Re: Isolatable Concerns
    ... In relational thinking, what is together or apart is considered a ... difficult for humans to navigate unless they reflect a familiar ... Why sprinkle SQL around, especially if its redundant? ...
    (comp.object)
  • Isolatable Concerns (was: Transaction Oriented Architecture...)
    ... In relational thinking, what is together or apart is considered a ... specific viewpoint. ... things as physical lumps that are either together or not together ... you could potentially group and edit all SQL together on your ...
    (comp.object)
  • SQL 2005 servers with multiple instances
    ... I have an interesting configuration that I was hoping others might comment ... consider the two servers with many small drives for the 'Live' data ... is being shared for the Live data and the Redundant data/logs. ... To my knowledge, SQL provides no prioritization, other ...
    (microsoft.public.sqlserver.setup)
  • SQL::Interpolate - request for comments
    ... as I was writing a lot of SQL construction/variable binding code ... (similar to Recipe 14.13--Building Queries Programmatically, Perl ... The purpose of SQL::Interpolate is to make writing SQL queries in Perl ... more natural, less redundant, and less error-prone. ...
    (perl.dbi.users)
  • Re: Searching?
    ... replaced by SQL sometime in the late seventies. ... What, totally redundant? ... Adam ...
    (microsoft.public.access.modulesdaovba)