Since you are looking-up by fur and lets, build a hash with the keys and values you need, instead of by ID: 
## Instead of ## my %lookup_id = map { $_->{id}, $_ } @rows;
my %lookup_fur_and_legs;
push (@{ $lookup_fur_and_legs { $_->{fur} . $_->{legs} } }, $_ ) for  
+@rows;

# This now allows, given any fur-legs combo : $fl,
for my $row (@{ $lookup_fur_and_legs{$fl} } ){
   # WHatever you want with each row for thes $fl ...
}

[download]
But, as BUK indicated, filtering is better done by SQL against a database.

             When in doubt, mumble; when in trouble, delegate; when in charge, ponder. -- James H. Boren

In reply to Re: Creating SELECT-like look-up tables as hashes by NetWallah
in thread Creating SELECT-like look-up tables as hashes by loris

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.