Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

Re^2: Quickest way of fetching a Single row and column in MySQL using DBI

by cees (Curate)
on Aug 07, 2006 at 01:04 UTC ( #565881=note: print w/ replies, xml ) Need Help??


in reply to Re: Quickest way of fetching a Single row and column in MySQL using DBI
in thread Quickest way of fetching a Single row and column in MySQL using DBI

Although your version works, it is potentially open to an SQL injection attack through the $username variable. With DBI that is easy to avoid by using placeholders. Also, I think you want selectrow_array (selectrow_arrayref returns a reference to an array, wheras selectrow_array will return a list, or just a scalar value if you are selecting a single column).

my $id = $dbh->selectrow_array("SELECT id FROM users where username = +?", {}, $username);


Comment on Re^2: Quickest way of fetching a Single row and column in MySQL using DBI
Download Code
Re^3: Quickest way of fetching a Single row and column in MySQL using DBI
by perrin (Chancellor) on Aug 07, 2006 at 16:15 UTC
    I think you need array context there:
    my ($id) = $dbh->selectrow_array("SELECT id FROM users where username += ?", {}, $username);

      Scalar context works as well according to the DBI source code:

      sub selectrow_array { my $row = _do_selectrow('fetchrow_arrayref', @_) or return; return $row->[0] unless wantarray; return @$row; }

      The docs hint that this should work as well, but don't explicitly state it. Instead the docs mention this:

      If called in a scalar context for a statement handle that has more than one column, it is undefined whether the driver will return the value of the first column or the last. So don't do that.

      Anyway, it won't hurt to add the brackets in there to force list context, but it shouldn't be required.

        Quoting the DBI docs is insufficient because the DBDs can override this. Forcing array context is not required because only a single column is being fetched regardless of which DBD is in use. Whenever more than one column is being fetched you should force list context if you care at all about portability. In scalar context, some DBDs return the first of the multiple columns and some return the last. Personally I try to always force the list context since it doesn't ever hurt and it sometimes helps.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://565881]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (10)
As of 2014-12-18 09:59 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (48 votes), past polls