On Thu, Jul 14, 2005 at 04:15:53PM +0200, Jochen Wiedmann wrote: > On 7/14/05, Sam Vilain <[EMAIL PROTECTED]> wrote: > > > Of course it will be entirely possible to layer support for this sort of > > thing atop any DBI interface; > > Exactly my point. Please be so kind as to implement your ideas in a > DBI extension. Time and community will prove whether you are right by > using your extension or not.
*nod* > Fact is, that there are quite some drivers which will never be able to > adhere to your wishes. Blocking them implementing a DBI2 driver seems > (to me) to be a larger problem, compared with the need of using a DBI2 > subclass and not DBI2 directly. The key design issue here is not "can the DBI do it" but "can the DBI make it possible to implement X elsewhere". The DBI is fundamentally a low-level interface to database-specific APIs with just enough sugar to make it palatable. I hope DBI v2 will polish up some rough edges and make more things possible - rather than actually doing much more itself - but it'll remain a low-level interface to database-specific APIs. If it can be done outside the DBI it probably should. Tim.
