Like many monks rewrite code to
improve it, I am going to rewrite the first three paragraphs
in the attempt to add a touch of tact to them:
Thank you for contributing gmax, that is an impressive
start of a cookbook. But ... shouldn't you have incorporated
more error checking and transaction support? These are,
IMHO, an integral part of DBI - actually, I strongly feel
that there's no excuse to not wrap your database modifying
statements inside a transaction, and to not rollback on
failure. Along those lines, one could accuse your examples
of being equivalent to Perl code that isn't strict, doesn't
have warnings turned on, and isn't checking the return
values of system calls.
By the way, Re: Style, *again* appears to be the only node where you actually thanked someone here. Many, many have thanked
you in the past - you should return the favor more often, if nothing more than for being appreciated.
Years ago my mother used to say to me, she'd say, "In this world, Elwood, you must be" -- she always called me Elwood -- "In this world, you must be oh so smart or oh so pleasant." Well, for years I was smart. I recommend pleasant. And you may quote me.
Elwood P. Dowd
-
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.
|