Subject | Re: [ib-support] Please remove the ambiguity check |
---|---|
Author | Martijn Tonies |
Post date | 2001-12-06T17:30:40Z |
Hi,
The check was build in to avoid 'random' results - it isn't/wasn't defined
what the results would be if you have an ambiguity. Ambiguity should be
rejected - in your query, you can use 'ORDER BY 1'
Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
> SELECT A.*, B.* FROM TABLEA ANo.
> LEFT OUTER JOIN TABLEB B
> ON A.ACCOUNT_NUMBER = B.ACCOUNT_NUMBER
> ORDER BY ACCOUNT_NUMBER
>is not ambiguous. But RC1 says it is, because RC1 assumes that the
>value of ACCOUNT_NUMBER in both tables could be different.
>Why can't RC1 do its best to understand the query, and maybe give a
>warning if there is ambiguity, and run it anyway. Leave it up to the
>developer to remove ambiguity.
>This is IMPORTANT. Is there anyone out there who agrees with me?
The check was build in to avoid 'random' results - it isn't/wasn't defined
what the results would be if you have an ambiguity. Ambiguity should be
rejected - in your query, you can use 'ORDER BY 1'
Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."