Tim Bunce wrote: > And it's not good I'm afraid. You've effectively hardwired a specific > driver in place of the DBI.
What I sent you is a proof of concept, not a final product (tho it works for its one driver). > It only emulates the DBI in the narrowest > sense. You can't use it to load and run any random pure-perl driver. I wanted to hear from you whether this project is even worth doing before implementing that. I'd previously done some preliminary tests with DBD::XBase and it seems to work well. Obviously it can work with DBD::CSV and DBD::Excel and any other drivers that use SQL::Statement. I totally agree it should work for all pure-perl drivers. > And that's a pity because there's (probably) no big technical issues > in creating a true pure-perl DBI with a reasonable level of functionality > (but much slower performance). Is this a project worth embarking on? If so it would proabably be best as a team effort pooling resources of all the pure perl driver authors and whomever else might want to contribute. > DBI::PurePerl would start with 'package DBI;' and define all > the functions and methods that DBI.xs currently does. My previous thinking was more along the lines of providing only the basics so that no one would be tempted to use it when they really should be switching to DBI. -- Jeff
