Because org.postgresql.Driver#jdbcCompliant() returns false. So you can ignore that for now, and I'm sure that the PostgreSQL JDBC people would like code contributions
(Go Raiders ! )
Thanks Jesper - mystery solved! Seems like an easy fix for Postgres - I may checkout the source code and take a look at it.
And I would tell you where I would like the Raiders to go, but this is a G-rated forum!
Well, there is more to it than changing the method implementation, but the PostgreSQL JDBC people can give you an idea what is missing.
Still feeling the pain from week 1, eh ?
In the postgresql jdbc api:
public boolean jdbcCompliant()
Report whether the driver is a genuine JDBC compliant driver. A driver may only report "true" here if it passes the JDBC compliance tests, otherwise it is required to return false. JDBC compliance requires full support for the JDBC API and full support for SQL 92 Entry Level.
For PostgreSQL, this is not yet possible, as we are not SQL92 compliant (yet).
- Specified by: