Subject RE: [firebird-support] Table aliases - SQL standards requirements & best practice
Author Svein Erling Tysvær
Did you notice

As Michael Ludwig said, aliases are required when doing a self join. Otherwise, I generally prefer them due to table names often being a bit long and repeated table names for each field in a query (whether in the SELECT, JOIN or WHERE clause) tend to make it slightly more difficult to read (IMO). If a query only involves one instance of one table like 'SELECT name FROM customer where id = :id', then a table alias would be pointless (of course), but once two or more tables are JOINed I always prefer an alias - even if field names are different in each table (it makes the query easier to read for persons not knowing the structure of your tables).


-----Original Message-----
From: [] On Behalf Of Peter Bailey
Sent: 4. mai 2010 08:29
Subject: [firebird-support] Table aliases - SQL standards requirements & best practice

Hello list

In Firebird 2.x according to the Release Notes "Alias handling and
ambiguous field detecting have been improved."

I would appreciate direction to a web site that will describe what is
required wrt Table Aliases and what is considered to be best practice.
(So far my searches have only found sites that show Table Aliases as
being a nice option.)