On Wed, 2003-08-13 at 17:30, Matt Sergeant wrote: > Unfortunately Apache::DBI is an ugly "action at a distance" hack :-)
I agree, but having everyone implement their own is worse. It leads to lots of repeated work on solved problems. What would you suggest to fix it? My idea would be to leave Apache::DBI as it is for use with legacy CGI code and then add a new module to the distribution that is called explicitly so it has no "distance" issues. Maybe call it Apache::DBI::Factory? There could also be an attempt to reconcile Apache::DBI with DBI->connect_cached. AFAIK, the only features Apache::DBI has over connect_cached are the rollback cleanup handler and the transparency part, which we don't like. Apache::DBI::Factory could just call connect_cached and add the cleanup part. - Perrin
