On Thu, Dec 02, 2004 at 08:53:38AM +0100, Cosimo Streppone wrote: > Tim Bunce wrote: > > >I know what it does, I'm trying to find real examples that demonstrate > >why people think it's needed. Nick has provided a good one. Any others? > > Something like DBIx::DBH is in use in our organization. > This is because every sql "source" (meaning database table) > is accessed with standard objects and an external definition file > like: > > USER john > PASS smith > DBNAME <default> > FILE sessions > HOST my.hostname.com > PORT 1521 > > # ... > # Definition of table fields > myfield1 ... bla bla blah > myfield2 ... bla bla blah > > Thus, every piece of information needed for connection *should* > be separated and a frontend is provided to be able to define new > sources or modify existing sources from a browser. > > Then, we provide different sql "driver" modules, that assemble > the DSN string given all the pieces.
None of that addresses the "why" question. All could be done by storing the DSN. Then you'd also be able to specify both DBI and driver-specific attributes, which it looks like you can't currently. Tim.
