Good Morning Peter- The way I read it is that DBI is one of those OO concepts which if implemented in OOD (Java?) would have worked beautifully DBI conceptually is a package of classes which would (supposedly) allow anyone to write to any DB regardless of underlying provider and or interface
The problem is while one forward looking developer is using DBI another one can write using legacy DBD package (to write to the same DB directly) so the problem of vast reams of unmaintainable and un-architected direct calls to your DB via DBD attempt must somehow peacefully co-exist with higher level DBI advocates.. What happens when you go to Transaction based model in DBI but the DBD folks balk? What happens when you decide to implement Connection Pooling but the DBD folks balk? What happens when you decide to upgrade DB's but the DBD folks have hardcoded connection strings and cause delay in up-migration strategy? DBI is an idea to abstract away underlying Transports/interfaces ~ but like all good ideas must be universally accepted BY ALL DEVELOPERS to make it work A high level overview is available here http://dbi.perl.org/about/ Martin -- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. ----- Original Message ----- From: "Peter J. Holzer" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, September 20, 2006 8:50 AM Subject: Re: Migration dbi files ?
