in reply to SQL Library modules - DBIx::QueryByName

appear to be a violation of orthogonal integration of concerns

... I know half the battle in understanding something is to grok the vocabulary, and I'll have to meditate a long time to figure that one out..... of course...I'm not much of an SQL person :-)

P.S. ... ah, I think I understand now..high level design strategy

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku
  • Comment on Re: SQL Library modules - DBIx::QueryByName

Replies are listed 'Best First'.
Re^2: SQL Library modules - DBIx::QueryByName
by metaperl (Curate) on Nov 02, 2009 at 14:16 UTC
    orthogonal integration of concerns
    let's take DBIx::Password as an example, it confuses the concern of storing the configuration info for connecting to a database with the concern of connecting to a database.

    Connecting to a database is best handled by DBIx::Connector. Application configuration information is best handled by (pick your favorite config module, I like a Moose class myself). Orthogonal integration of these two modules is one way to get database connections. The other way is violation orthogonal integration of concerns and try to lump it all in a single module like DBIx::Password.

    Now, this SQL Library module does a similar thing. It tries to handle database sessioning AS WELL AS sql cataloging. Yet another violation of orthogonal integration of concerns

[reply]
      orthogonal integration of concerns

      from my background, if something is truly orthogonal, it means it adds another dimension to the set..... this seems desirable to me... more dimensions, which can or can't be used.... too much Matrix algebra in school... :-)

      but i do see the different context that you give to orthogonal

      I'm not really a human, but I play one on earth.
      Old Perl Programmer Haiku
[reply]

In Section Meditations