While you may have a point your arguments do show why it is often difficult to have negative reps on modules. There are ratings, bug reports and documentation for a reason. After reading the docs and (where necessary) experimenting with the module you are in a position to decide whether it meets your needs.

For example, your initial point:

#  Class::DBI::Pager - that module does not use 'LIMIT' clauses in the
+ database, there are better alternatives.
[download]

I use SQL server. Additionally, a brief (very brief) scan of the alternatives - well one doesn't support Oracle or DB2. So I have to write my own limit syntax/code anyway. As my workplace uses those three DBs exclusively. No postgres and no mysql. Period.

I'm not saying your criticism is not unfounded, but it doesn't help me as the syntax you complain about is not available to me regardless.

Would it not be better to offer solutions to problems?

Finally, you recommend an experimental module as part of your "review". Where I work, experimental code cannot go on a production system. Period.

Just my 2p so please take in the same vein :).

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.