On Fri, Oct 12, 2012 at 5:18 PM, Justin Deoliveira jdeol...@opengeo.orgwrote:
Ahh cool. Good to know.
I will probably still parameterize the version at some point though so we
can run unit tests against postgres 8 and 9 easily.
Sounds like a good idea.
In the past I've tried an upgrade a
Justin,
see also this Jira issue from February. If you upgrade the driver and
fix this failure, please resolve the issue:
Support PostgreSQL 9 hex bytea output format to avoid massive data
corruption
https://jira.codehaus.org/browse/GEOT-4040
Kind regards,
Ben.
On 12/10/12 21:08, Justin
That is also in the Jira issue!
https://jira.codehaus.org/browse/GEOT-4040
If we upgrade the driver, do we fix it for everyone?
On 12/10/12 21:30, christian.muel...@nvoe.at wrote:
Hi Justin
I found another solution:
If you use a postgres driver lower than version 9 you can prepare your
Long story for short. The postgis raster online test was broken and
the fix is to update the postgres driver version. The module will not
work with 8.x postgres drivers.
The global pom contains
dependency
groupIdpostgresql/groupId
artifactIdpostgresql/artifactId
I would use a property to make this configurable. Indeed I ran into this
same problem when trying to run postgis tests against a postgresql 9.1
database. The protocol for blobs has changed which caused those tests to
fail. Since we want to support both major versions of postgresql it makes
sense
Hi Justin
I found another solution:
If you use a postgres driver lower than version 9 you can prepare your
database
with
ALTER DATABASE dbname SET bytea_output TO 'escape';
I will kick out my version tag, prepare my test database and add
this info to the user guide. I think this is the
Ahh cool. Good to know.
I will probably still parameterize the version at some point though so we
can run unit tests against postgres 8 and 9 easily.
-Justin
On Fri, Oct 12, 2012 at 7:30 AM, christian.muel...@nvoe.at wrote:
Hi Justin
I found another solution:
If you use a postgres driver
