Don't get me wrong -- I think you should submit this to CPAN. The module is well-written, documented and serves a specific purpose. IMO competition is good, and one of the unfortunate things about CPAN modules is that many of them are heavily upgraded for ~6 months and then abandoned. If you maintain your module for the long-haul, keeping up with upgrades to the DBI, then you'll be a step ahead in my book.

That said, I think the comparisons you draw with the other modules are distinctions without differences. They do much the same tasks but just in different ways. Some ways might fit the way a developer approaches a problem, some might not. None of these modules fit your approach enough to contribute to it rather than develop your own. No problem.

Fortunately, there's not an all-powerful gatekeeper to CPAN who gives the thumbs-up or thumbs-down to a module. IMO this is one of the features of Perl that makes it organically vital. The fact that there are so many DBI wrappers (and templating modules) means this is a problem everyone tackles, and problems like this are often too generic to have one solution. This might annoy or turn away developers from other languages, particularly ones that have been handed down from the mount (Java), but so what?

Keep up the great work!

Chris
M-x auto-bs-mode

In reply to Duplicating work and CPAN by lachoy
in thread DBIx::Simple by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.