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.
Juerd, as the reviews show, this is a great module. It's my favorite way to access Perl databases. However, there are some issues with the module that are not receiving a timely response.

REPO

I emailed you 2 weeks ago about putting the source code for ::Simple in a public repo and you said you might, which is not definitive and doesnt encourage collaboration.

MAP_FIELDS

I demonstrated the utility of a map_field method and you did not agree to add one. I need one. It seems a good companion to map_hashes

OUTSTANDING BUGS

There are 2 active bugs, both over 5 months old that you have not responded to or addressed.

NO RESPONSE TO EMAILED BUG

48 hours ago, I emailed you another issue along with a test case, and you have said nothing. I repeat it below for others to confirm/observe:

unorthodox scalar weakening leads to premature statment handle destruction

Hi Juerd.
  1. any further thoughts on a public repo?
  2. if you download this folder and run test.pl, you will note that Case 3 returns a destroyed object because of the use of method chaining ( $dbixsimple->query->hashes ) . If line 165 in DBIx/Simple.pm has the quote marks removed from $self, then this case works fine, just like Case 1 and Case 2.

    The problem is caused by line 158 in your code, where you attempt to hide a reference to the database handle by double-quoting it within the statement handle.

    Is there a reason you didnt use Scalar::Util::Weaken instead of quoting an object like that? And why was such manual reference counting necessary anyway?

CONCLUSION

DBIx::Simple is a wonderful module, but it is in need of upkeep.



The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development.

-- Terence Parr, "Enforcing Strict Model View Separation in Template Engines"

In reply to Re: DBIx::Simple - Your opinions/review please by metaperl
in thread DBIx::Simple - Your opinions/review please 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.