|Subject||Re: [IBO] How to access field when there are dupe field names|
> > ... That's why SQL provides aliasing - to resolve suchThe official (SQL) qualified column name would be:
> > redundancies.
> > ...
> > Therefore, you are up the creek if you refuse to use aliases to
> > resolve redundancies and simplify what you do with IBO.
> > ...
> > However, if you insist on avoiding the aliasing...
> Here's another reason why I prefer to avoid aliasing: Column aliases
> can't be used in calulations, JOIN conditions, ORDER BY and GROUP BY.
> Building queries in code becomes is thus further complicated, becuase
> in some places (column list) I must use aliases, and in other places I
> must *not* use aliases.
> If only IBO supported fully qualified column names everything would
> have been much simpler.
Given that a column name can be _anything_ in a resultset, and not
tied to a table.
You're not working with tables, you're working with resultsets.
A resultset is a derived table.
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL