How to reproduce it:
1.- define in Client window attachments on file system
2.- Select in any window for any record an attachment
3.- when you save the attachment, you get in the eclipse console the error "Content is not allowed in Prolog" while parsing the data
If you do the same on Postgres 8.4, there is no problem.
Best regards,
Mario Calderon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
before the patch is applied, here the procedure how to overcome it (thanks to Victor for the hint):
1.- go to http://jdbc.postgresql.org/download.html
2.- download Driver: 9.0-801 JDBC 4
3.- change driver file name from postgresql-9.0-801.jdbc4.jar to postgresql.jar
4.- replace in trunk old postgresql.jar with new postgresql.jar (in /lib, /tools/lib and /db/ddutils/lib).
I think in ddutils it doesn't matter, but it's better to replace it there, too.
BTW, we have tested Postgres 9 with good results so far.
Best regards,
Mario Calderon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Estimado Mario. Casualmente hoy me tocó lidiar con este mismo problema. Después de un poco de investigación llegué a que, a partir una de las versiones 9 de PostgreSQL, el formato de muestra de los campos blobs pasaría a ser hexadecimal. Me imagino que en el código no espera este cambio.
La solución para mí fue el siguiente SQL en la bd:
ALTER DATABASE database_name SET bytea_output TO 'escape';
Saludos!
PD: Saludos desde Venezuela Mr. Victor
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I can confirm this message.
How to reproduce it:
1.- define in Client window attachments on file system
2.- Select in any window for any record an attachment
3.- when you save the attachment, you get in the eclipse console the error "Content is not allowed in Prolog" while parsing the data
If you do the same on Postgres 8.4, there is no problem.
Best regards,
Mario Calderon
The issue is because the binary file was change in PostgreSQL9 the solution is update the JDBC for this version.
http://adempiere.hg.sourceforge.net/hgweb/adempiere/adempiere/rev/5c58709744f0
http://adempiere.hg.sourceforge.net/hgweb/adempiere/adempiere/rev/f27508ca1197
kind regards
Victor Perez
www.e-evolution.com
Hi,
before the patch is applied, here the procedure how to overcome it (thanks to Victor for the hint):
1.- go to http://jdbc.postgresql.org/download.html
2.- download Driver: 9.0-801 JDBC 4
3.- change driver file name from postgresql-9.0-801.jdbc4.jar to postgresql.jar
4.- replace in trunk old postgresql.jar with new postgresql.jar (in /lib, /tools/lib and /db/ddutils/lib).
I think in ddutils it doesn't matter, but it's better to replace it there, too.
BTW, we have tested Postgres 9 with good results so far.
Best regards,
Mario Calderon
Estimado Mario. Casualmente hoy me tocó lidiar con este mismo problema. Después de un poco de investigación llegué a que, a partir una de las versiones 9 de PostgreSQL, el formato de muestra de los campos blobs pasaría a ser hexadecimal. Me imagino que en el código no espera este cambio.
La solución para mí fue el siguiente SQL en la bd:
ALTER DATABASE database_name SET bytea_output TO 'escape';
Saludos!
PD: Saludos desde Venezuela Mr. Victor