Re: Avoiding New Fields Causing Ambiguity Errors

From: Bob Hairgrove <rhairgroveNoSpam_at_Pleasebigfoot.com>
Date: Tue, 07 May 2002 19:15:15 GMT
Message-ID: <3cd827a2.773452_at_news.ch.kpnqwest.net>

On 7 May 2002 11:35:49 -0700, topmind_at_technologist.com (Topmind) wrote:

>Title: Avoiding New Fields Causing Ambiguity Errors
>
>[SNIP]
>Is there any "best practices" standards that deal with this issue?

Yes ... always alias the table names in any query which involves more than two tables and include the alias in the SELECT list for each column (or else include the table name verbatim). Don't leave this to chance.

Bob Hairgrove
rhairgroveNoSpam_at_Pleasebigfoot.com Received on Tue May 07 2002 - 21:15:15 CEST

This message: [ Message body ]
Next message: Jan.Hidders: "Re: database design"
In reply to Topmind: "Avoiding New Fields Causing Ambiguity Errors"
Next in thread: --CELKO--: "Re: Avoiding New Fields Causing Ambiguity Errors"
Reply: Topmind: "Re: Avoiding New Fields Causing Ambiguity Errors"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message