I am really surprised at how far you have followed this
Matts, your original post to the dbi-dev included:
in reply to Would you use SQLite?
"Anyway, this is my first hack at a DBD driver, so it's likely buggy,
leaky, etc. But seems to work for the simple selects I've run on it so
far. I've done no optimization, no performance tests, or anything. I
literally hacked this together today for fun. And I'm not particularly
looking to maintain it unless there's really strong interest in it, and
even then I'd rather someone offered to take it over."
I had assumed (falsely) that it was more of a programming
exercise. Now it seems (here I go assuming again) that you
are very interested in how this module is regarded by the
My opinions on this?
- The DBIx and DBD namespace is polluted right now. The number
of choices is almost overwhelming for new comers.
- I like using MySQL as a database and it is convient for
*me* to do that.
- I am interested in DBD::SQLite, but I haven't
taken the time to play with it. So maybe I am not
- I would be more interested if a clear benefit in
using it over the other currently available solutions was
- I don't consider speed enough of a benefit.
- Issues like number of users, remote access, support, etc. would contribute to my use of the module.
- Since you indicate(d) you are not interested in maintaining
I am not likely to invest time into until someone does
take over maintaining it.
In short I am looking for a compelling reason to