Nazish Khan

UCanAccess exhibits a cleaning behavior where it doesn't raise an error when a column name in a SQL query is ambiguous, unlike many other database engines that do. Instead, UCanAccess appears to prioritize the first table in the FROM clause that contains the column with the same name. This differs from the behavior of databases like Access, SQL Server, MySQL, DB2, and Oracle, which explicitly flag such situations as errors. Is there a configuration option or a way to modify UCanAccess to align with...