>>>It really requires a large scale project to reap the benefits and be worth the performance hit you take vs. doing traditional SQL queries.<<<
Blah! I really don't see why someone would adopt this view. Unless you are doing something very minimal to your database, which almost flies in the face of setting up a database to begin with... I don't think the performance hit is that much compared to the orderliness and re-factorability one automatically brings to their Perl by going with an OO interface to the database.
If I have to do more than 1-2 things with the database, I go Class::DBI. It's just as fast as setting up all the dbh and sth handles and it's much more orderly. You're not using Perl for speed anyway, so what's the big deal anyway?!
-
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.
|
