But this is a religious issue with me. As long as the RDBMS supports it, you should use ANSI 92 join syntax. And you should use table aliasing as well. So your query ought to be written as 
select st.supplier
from supplier_table as st join supplier_item_xref as six
      on st.id = six.supplier_id
   join item_table as it on six.item_id = it.id
where it.item in ('screw', 'stereo');

[download]
This allows the SQL optimizer to do a better job and can result is faster code for complex joins. If your RDBMS doesn't support this, upgrade. It makes your code more readable. --Shoeboy
I'm not wearing any pants

In reply to I hate to be picky... by Shoeboy
in thread DBI vs MLDBM/GDBM_File, etc. by ZZamboni

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.