I'd like to suggest that we:
1. update geotools so it uses this jar instead of an earlier one (requires maven 1 and maven 2 magic)
2. update geoserver so it also uses this jar (just replace the jdbcPostresql.jar jar with the above one)
I have no idea how to do (1), but (2) is trivial.
dave
ps. this is the latest "stable" release of the postgresql JDBC driver. The one that appears to be currently used is "postgresql-74.213.jar".
I'd like to suggest that we:
1. update geotools so it uses this jar instead of an earlier one (requires maven 1 and maven 2 magic)
I already posted an email suggesting the same (for different reason) two weeks ago. Since I got no objection, I already upgrated the Maven 2 build on trunk to the following version:
8.1-404.jdbc3
This is 404 instead of 405 only because the 404 version was the only one available on http://www.ibiblio.org/maven2/ (the Maven 2 repository) last time I looked.
Please review the developers guide for instructions about posting a new third party jar into the maven repository. If this is not fixed by Mondays meeting I will upload it then...
Jody
I've noticed a few problems with an older version of the Postgresql JDBC driver.
This had to do with detecting encoding of data in the database. I've been using:
I'd like to suggest that we:
1. update geotools so it uses this jar instead of an earlier one (requires maven 1 and maven 2 magic)
I already posted an email suggesting the same (for different reason) two weeks ago. Since I got no objection, I already upgrated the Maven 2 build on trunk to the following version:
8.1-404.jdbc3
This is 404 instead of 405 only because the 404 version was the only one available on http://www.ibiblio.org/maven2/ (the Maven 2 repository) last time I looked.