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