adopt documentation wr/t conflicting driverconfig.properties to

reflect what jdbc actually does.

git-svn-id: http://svn.osgeo.org/postgis/trunk@1388 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/jdbc2/README b/jdbc2/README
index e2dc14da5b56e086a41712269c2579f8a2f8528f..2ed1c2ccb29703485fc61a7cc8896c7dd062d8d4 100644 (file)
--- a/jdbc2/README
+++ b/jdbc2/README
@@ -157,7 +157,7 @@ autoregister for the same PostGIS types, as the driver cannot guess
 which extension it should actually use on which connection. The
 current pgjdbc implementation simply parses all
 org/postgresql/driverconfig.properties the classloader can find in his
-classpath, and later definitions override earlier ones.
+classpath, using the first definition found for each type.
 
 
 * How to I run the tests? Are they allowed to fail? *