How many joins do you do in your case?

Like your example code, I use as many joins as I have distinct criteria. We typically only have a couple of sets of criteria, but sometimes it's five or six, and the performance on MySQL has been fine.

Here is the code i came up with so far.

I'd like to reiterate the importance of using placeholders, which allow for efficient query plan caching.

You could easily modify your sample code to return a parameterized query based simply on how many criteria pairs you had. You can then pass your pairs of meta-data criteria to the DBI as execute() parameters. It eliminates any worries about quoting and escaping the values, and may provide a performance benefit by simplifying the database's query parse/plan efforts. 

sub GetNodes {
  my $meta = shift;
  my $sql = buildMetaQuery( scalar keys %$meta );
  my $sth = $dbh->prepare_cached($sql);
  $sth->execute( %$meta );
  $sth->fetchrow_array  
}

[download]

This assumes that buildMetaQuery( 3 ) returns something like: 

SELECT md1.node_id
 FROM `meta_data` as md1,`meta_data` as md2,`meta_data` as md3
 WHERE md1.name = ?
   AND md1.value = ?
   AND md2.name = ?
   AND md2.value = ?
   AND md3.name = ?
   AND md3.value = ?
   AND md1.node_id = md2.node_id = md3.node_id;

[download]

In reply to Re: Re: Re: Re: Querying Meta Data by simonm
in thread Querying Meta Data by eric256

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.