I'd argue that 'fully qualified' is a misnomer in databases.
What should be sent when your 'table' is really a view? Do you send the underlying table, or the view's information? What do we send for calculated fields? What about database links (for those databases that support 'em)?
I'd agree with perrin -- just use column aliases, and you'll be fine. Of course, depending on what's actually in your database, I foresee problems unless there's a UNIQUE constraint on work_phone(people_id,phone_type). (ie, there's only one work / fax / whatever type of number per person).
If there isn't this constraint, it might be easier to not do as many table joins, and just handle the assignment of the phone type in logic once you've retrieved the logic. If there is the constraint, consider using a view to handle the denormalization (and hardcode the phone_types).
In reply to Re: getting fully qualified column names (mysql)
by jhourcle
in thread getting fully qualified column names (mysql)
by metaperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |