'UCanAccess allows ambigious column names
It appears that UCanAccess does not complain when a column name appearing in the SELECT clause, WHERE clause, etc. is ambiguous. Instead, it seems that the first table in the FROM clause that has a column with that name is used. This is a very dangerous behaviour that most other database engines reject. For example Access will respond with an error message "The Specified field 'something' could refer to more than one table listed in the FROM clause of your SQL statement". Similarly SQL Server would complain with the message "Ambiguous column name 'something'". MySQL complains with the message "Column 'something' in field list is ambiguous". DB2 responds "A reference to column "something" is ambiguous". And Oracle responds "column ambiguously defined".
Is it possible to fix this in UCanAccess? Is there a way to configure this behaviour?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|