Fellow Monks,
if you spend a lot of time working on something, after a while things get blurry. DBIx::Simple recently got a lot of it re-coded, it was refactored and some features are deprecated. All user suggestions that I could track have in some way been dealt with. This resulted in a lot of "It's already there, if you look for it" and some "Sorry, I don't think that belongs in a *Simple* module", but also a bunch of new features. As said, things get blurry.
Perhaps something very important is missing, but just like my brain learned to ignore the mess in my office, I no longer see the code of DBIx::Simple clearly.
Last time, I waited a long time before releasing the new version. But that didn't really work well. DBIx::Simple is used in a lot of production environments, and I'd like to release bug fixes soon, and would like to introduce new simplifying features more often. That way, maybe people won't have to hack it and mess with its internals. (Although the recently added dbh and attr methods should avoid having to hack.)
One thing is missing that I know of. A test suite. To be honest, testing is one of my weaknesses. I know that I like having tests to rely on, and that I don't mind adding tests when I add new features. But I hate writing a test suite from scratch, especially for a module that I've been using for over two years already. Fortunately, someone volunteered to write a complete and thorough test suite for this module. Because of the circumstances, this has been delayed a few times already, but eventually, DBIx::Simple will have tests. So please don't complain about that.
As some readers will know, I'd like to know how many people use DBIx::Simple, or on how many boxes it is installed, or even how often it is downloaded. I'm not yet going to automate that, because I'd first like to know how people use DBIx::Simple.
I'm not asking you if you use it privately or commercially, I don't care if it's for an application that one person will use or for one that thousands rely on. (But if you want to tell me, please go ahead.) Things I'm very interested in right now are:
- Do you use it for throw away scripts, in production, both?
- How many queries happen per second? How large are the results (in rows, kilobytes)? (millions of tiny queries, tens of larger ones, etc)
- Do you use any of the currently deprecated features?
- What DBDs do you use it with?
- Do you use the "(??)"-thing? What's your opinion on having more like these, for example for easier use with INSERT and UPDATE?
Another thing I'm interested in, is what you think about DBIx::Simple in general. Is it fast enough? Does it focus on speed too much? Should it have less or more features? Is it just about right? How is the documentation? Do you hate or love its source? Is the Changes file detailed enough? Should I not be using EU::MM?
In case you haven't used DBIx::Simple yet, please do give it a try and let me know how things went. I'd really appreciate a thorough review, especially from someone who has experience with DBI and/or DBIx modules.
I might not like your suggestions. But I will read what you have to say and think about it.
Thanks in advance for helping me develop DBIx::Simple further.
<shameless>I wouldn't mind some more ratings =)</shameless>
Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: DBIx::Simple - Your opinions/review please
by simonm (Vicar) on May 30, 2004 at 16:34 UTC | |
by Juerd (Abbot) on May 30, 2004 at 20:50 UTC | |
by hv (Prior) on May 30, 2004 at 21:54 UTC | |
by Juerd (Abbot) on May 30, 2004 at 22:33 UTC | |
DBIx::Simple 1.23 (Re: DBIx::Simple - Your opinions/review please)
by Juerd (Abbot) on Jun 11, 2004 at 11:08 UTC | |
A reply falls below the community's threshold of quality. You may see it by logging in. |