I think this bug sums up my quandry perfectly:
It makes no sense that I can use fully qualified names in the query, but results can not be returned fully qualified as well.

I have a situation where I need to select from the same table twice - I need to get the work and fax phone numbers for a person.

Now I can use table aliases to make each query of the phone table distinct (one such call shown: 

SELECT *
FROM agents
INNER JOIN people ON ( people.id = agents.people_id )
INNER JOIN phone AS work_phone ON ( work_phone.people_id = people.id
AND work_phone.phone_type = (
SELECT id
FROM phone_types
WHERE enum_name = 'Work' ) )

[download]
but there is no way to get back the results with the column names table-qualified.

So I am going to be forced to make the queries for phone one at a time because there will be a column name conflict.

In reply to getting fully qualified column names (mysql) by metaperl

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.