If the queries I'm working with are going to be fairly static, I'll
generally trade in my fetchrow_hashref calls for pseudo-hashes created
with fetchrow_array instead.
It generally ends up looking something like this: my $order = { col_one => 1, col_two => 2 };
my $sth = $dbh->prepare("SELECT col_one,col_two FROM table");
$sth->execute();
my $row = [$order, $sth->fetchrow_array()];
print "<LI>This is the data for col_one: $row->{col_one}</LI>";
Or something like that, the only downside being: if I change the SQL query
in my dbh->prepare() call, I'll have to make the corresponding changes to
the order hashref above. This saves the DBI overhead of having to check the
column names for each query, plus you get the benefits (IMO, at least) of
pseudo-hashes over plain hashrefs -- wether or not you like them is up to
you, here is one small discussion on the matter: Are pseudo-hashes worth the effort?
-
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.
|
