nikos dimtrakas

This was originally asked at stackoverflow according to the instructions on https://ucanaccess.sourceforge.net/site.html#about but never got answered. I am trying here. The standard behaviour of SQL is to require all non-aggregated columns appearing in the SELECT clause (or HAVING or ORDER BY) to appear in the GROUP BY clause. For example the following would fail (because of b not being aggregated and not appearing in the GROUP BY clause): SELECT a, b, COUNT(*) FROM t GROUP BY a Access will give...

This was originally asked at stackoverflow according to the instructions on https://ucanaccess.sourceforge.net/site.html#about but never got answered. I am trying here. 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...

This was originally asked at stackoverflow according to the instructions on https://ucanaccess.sourceforge.net/site.html#about but never got answered. I am trying here. There seems to be a bug or at least an unexpected behaviour when using the UCanAccess JDBC-driver. Is there an explanation or is it just a bug that should be fixed? Here is a simple example: ResultSet rs = statement.executeQuery("SELECT name, name n, name as n2 FROM Person"); ResultSetMetaData metaData = rs.getMetaData(); System.out.println(metaData.getColumnLabel(1));...