Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
OK, I have now *really* upgraded to the configuration I mentioned, namely: PostgreSQL 7.4 PG JDBC 7.3 Cocoon 2.1.4 Java 1.4.2 and my German and French diacritics come out OK. All I did was pg_dump the database in version 7.3.3 and then pg_restore it in version 7.4. On 1 Apr 2004, at 15:16, Yves Vindevogel wrote: Could you check with pg_configure what options were used ? [airport-5:~] steve% pg_config --bindir --includedir --includedir-server --libdir --pkglibdir --configure /usr/local/bin /usr/local/pgsql/include /usr/local/pgsql/include/server /usr/local/pgsql/lib /usr/local/pgsql/lib '--bindir=/usr/local/bin' '--mandir=/usr/local/man/' '--enable-recode' '--with-CXX' '--enable-odbc' '--with-java' '--enable-syslog' '--enable-unicode-conversion' '--enable-multibyte' '--with-openssl' '--with-perl' '--with-tcl' '--without-tk' 'LDFLAGS=-ltcl' In your setup, I see that you use JDBC 7.3. When I compiled, I ended up with 7.4 (not working) Could be a slip in that version. Do you mind sending me your compiled jar ? I'll send the JDBC jar directly to you. Cheers Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
Ahahhh, so that could be the reason Code slip in 7.4 On 01 Apr 2004, at 16:01, Stephen Winnall wrote: Yves I must apologise... I thought I had installed PG 7.4, but running pg_config for you revealed that I was in fact running 7.3.3. I will now install 7.4 and get back to you with an update. Sorry Steve On 1 Apr 2004, at 15:16, Yves Vindevogel wrote: Steven, I know it's wise to use a package somebody else build and tested. I did the same, but, I found out that it did not include all the languages I needed. Therefore, I recompiled myself. Could you check with pg_configure what options were used ? Same for Apache, for that matter. Not all compilations come with ProxyPass, which I use for linking Apache and Cocoon In your setup, I see that you use JDBC 7.3. When I compiled, I ended up with 7.4 (not working) Could be a slip in that version. Do you mind sending me your compiled jar ? I will conduct the same test as for 7.2 Yves On 01 Apr 2004, at 14:40, Stephen Winnall wrote: I'm glad Yves has found a work-around to his problem. However, I would like to point out that I am using the following together under Mac OS X 10.3.3: PostgreSQL 7.4 PG JDBC 7.3 Cocoon 2.1.4 Java 1.4.2 and a database containing French and German diacritics, and I have had no problem at all. I originally used PostgreSQL 7.3.3 and made no change to the database when I upgraded. It may be significant that I used Marc Liyanage's PostgreSQL package (http://www.entropy.ch/software/macosx/) rather than compiling the thing myself. Regards Steve On 1 Apr 2004, at 14:24, Yves Vindevogel wrote: Sure, but ... it's not only OSX related. I had the same problem too on Linux (Slack 9.1) Seems to be a bug in Postgresql 7.4 (maybe) or my compilation of the driver (now checking) Anyway, I think it should be put under a topic "Cocoon, file encoding and database (jdbc) encoding" I'll create my piece of that document. No problem with that. On 01 Apr 2004, at 14:08, Jorg Heymans wrote: Thank god you finally solved it ! :) Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows that it was never really a cocoon related problem but it could go into a "how to get postgres and cocoon to play well together on MacOSX" section. Regards Jorg Yves Vindevogel wrote: I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: *From: *Peter Mount <[EMAIL PROTECTED]> *Date: *Thu 1 Apr 2004 11:25:54 CEST *To: *Yves Vindevogel <[EMAIL PROTECTED]> *Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) * Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgresql and the jdbc driver that causes it most. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL P
Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
Yves I must apologise... I thought I had installed PG 7.4, but running pg_config for you revealed that I was in fact running 7.3.3. I will now install 7.4 and get back to you with an update. Sorry Steve On 1 Apr 2004, at 15:16, Yves Vindevogel wrote: Steven, I know it's wise to use a package somebody else build and tested. I did the same, but, I found out that it did not include all the languages I needed. Therefore, I recompiled myself. Could you check with pg_configure what options were used ? Same for Apache, for that matter. Not all compilations come with ProxyPass, which I use for linking Apache and Cocoon In your setup, I see that you use JDBC 7.3. When I compiled, I ended up with 7.4 (not working) Could be a slip in that version. Do you mind sending me your compiled jar ? I will conduct the same test as for 7.2 Yves On 01 Apr 2004, at 14:40, Stephen Winnall wrote: I'm glad Yves has found a work-around to his problem. However, I would like to point out that I am using the following together under Mac OS X 10.3.3: PostgreSQL 7.4 PG JDBC 7.3 Cocoon 2.1.4 Java 1.4.2 and a database containing French and German diacritics, and I have had no problem at all. I originally used PostgreSQL 7.3.3 and made no change to the database when I upgraded. It may be significant that I used Marc Liyanage's PostgreSQL package (http://www.entropy.ch/software/macosx/) rather than compiling the thing myself. Regards Steve On 1 Apr 2004, at 14:24, Yves Vindevogel wrote: Sure, but ... it's not only OSX related. I had the same problem too on Linux (Slack 9.1) Seems to be a bug in Postgresql 7.4 (maybe) or my compilation of the driver (now checking) Anyway, I think it should be put under a topic "Cocoon, file encoding and database (jdbc) encoding" I'll create my piece of that document. No problem with that. On 01 Apr 2004, at 14:08, Jorg Heymans wrote: Thank god you finally solved it ! :) Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows that it was never really a cocoon related problem but it could go into a "how to get postgres and cocoon to play well together on MacOSX" section. Regards Jorg Yves Vindevogel wrote: I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: *From: *Peter Mount <[EMAIL PROTECTED]> *Date: *Thu 1 Apr 2004 11:25:54 CEST *To: *Yves Vindevogel <[EMAIL PROTECTED]> *Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) * Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgres
Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
Please send my your .jar and please specify your encoding (in psql\encoding) I will test this too. Did you compile yourself or not ? I also had the problem with SQLTransformer. On 01 Apr 2004, at 15:12, beyaNet Consultancy wrote: Hi, for what it's worth, while using the following: OS X 10.3.3 postgreSQL 7.4.1 pg74.1jdbc3.jar (postgreSQL JDBC driver) Cocoon 2.1.4 Hibernate 2.1.1 I have had absolutely no encoding problems with postgreSQL. Maybe this can be attributed to using Hibernate as my persistence layer, and not using esql! Peter On 1 Apr 2004, at 13:40, Stephen Winnall wrote: I'm glad Yves has found a work-around to his problem. However, I would like to point out that I am using the following together under Mac OS X 10.3.3: PostgreSQL 7.4 PG JDBC 7.3 Cocoon 2.1.4 Java 1.4.2 and a database containing French and German diacritics, and I have had no problem at all. I originally used PostgreSQL 7.3.3 and made no change to the database when I upgraded. It may be significant that I used Marc Liyanage's PostgreSQL package (http://www.entropy.ch/software/macosx/) rather than compiling the thing myself. Regards Steve On 1 Apr 2004, at 14:24, Yves Vindevogel wrote: Sure, but ... it's not only OSX related. I had the same problem too on Linux (Slack 9.1) Seems to be a bug in Postgresql 7.4 (maybe) or my compilation of the driver (now checking) Anyway, I think it should be put under a topic "Cocoon, file encoding and database (jdbc) encoding" I'll create my piece of that document. No problem with that. On 01 Apr 2004, at 14:08, Jorg Heymans wrote: Thank god you finally solved it ! :) Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows that it was never really a cocoon related problem but it could go into a "how to get postgres and cocoon to play well together on MacOSX" section. Regards Jorg Yves Vindevogel wrote: I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: *From: *Peter Mount <[EMAIL PROTECTED]> *Date: *Thu 1 Apr 2004 11:25:54 CEST *To: *Yves Vindevogel <[EMAIL PROTECTED]> *Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) * Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgresql and the jdbc driver that causes it most. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Met vriendelijke groeten, Bien à vous, Kind regards, Yves Vindevogel Implements Mail: [EMAIL PROTECTED] - Mobile: +32 (478) 80 82 91 Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76 Markt 18c - 9700 Oudenaarde - Tel: +32 (55) 30 55 76 Web: http://www.implements.be First they ignore you. Then they laugh at you. Then they fight you. Then you win. Mahatma Ghandi. -
Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
Hi, for what it's worth, while using the following: OS X 10.3.3 postgreSQL 7.4.1 pg74.1jdbc3.jar (postgreSQL JDBC driver) Cocoon 2.1.4 Hibernate 2.1.1 I have had absolutely no encoding problems with postgreSQL. Maybe this can be attributed to using Hibernate as my persistence layer, and not using esql! Peter On 1 Apr 2004, at 13:40, Stephen Winnall wrote: I'm glad Yves has found a work-around to his problem. However, I would like to point out that I am using the following together under Mac OS X 10.3.3: PostgreSQL 7.4 PG JDBC 7.3 Cocoon 2.1.4 Java 1.4.2 and a database containing French and German diacritics, and I have had no problem at all. I originally used PostgreSQL 7.3.3 and made no change to the database when I upgraded. It may be significant that I used Marc Liyanage's PostgreSQL package (http://www.entropy.ch/software/macosx/) rather than compiling the thing myself. Regards Steve On 1 Apr 2004, at 14:24, Yves Vindevogel wrote: Sure, but ... it's not only OSX related. I had the same problem too on Linux (Slack 9.1) Seems to be a bug in Postgresql 7.4 (maybe) or my compilation of the driver (now checking) Anyway, I think it should be put under a topic "Cocoon, file encoding and database (jdbc) encoding" I'll create my piece of that document. No problem with that. On 01 Apr 2004, at 14:08, Jorg Heymans wrote: Thank god you finally solved it ! :) Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows that it was never really a cocoon related problem but it could go into a "how to get postgres and cocoon to play well together on MacOSX" section. Regards Jorg Yves Vindevogel wrote: I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: *From: *Peter Mount <[EMAIL PROTECTED]> *Date: *Thu 1 Apr 2004 11:25:54 CEST *To: *Yves Vindevogel <[EMAIL PROTECTED]> *Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) * Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgresql and the jdbc driver that causes it most. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Met vriendelijke groeten, Bien à vous, Kind regards, Yves Vindevogel Implements Mail: [EMAIL PROTECTED] - Mobile: +32 (478) 80 82 91 Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76 Markt 18c - 9700 Oudenaarde - Tel: +32 (55) 30 55 76 Web: http://www.implements.be First they ignore you. Then they laugh at you. Then they fight you. Then you win. Mahatma Ghandi. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
Steven, I know it's wise to use a package somebody else build and tested. I did the same, but, I found out that it did not include all the languages I needed. Therefore, I recompiled myself. Could you check with pg_configure what options were used ? Same for Apache, for that matter. Not all compilations come with ProxyPass, which I use for linking Apache and Cocoon In your setup, I see that you use JDBC 7.3. When I compiled, I ended up with 7.4 (not working) Could be a slip in that version. Do you mind sending me your compiled jar ? I will conduct the same test as for 7.2 Yves On 01 Apr 2004, at 14:40, Stephen Winnall wrote: I'm glad Yves has found a work-around to his problem. However, I would like to point out that I am using the following together under Mac OS X 10.3.3: PostgreSQL 7.4 PG JDBC 7.3 Cocoon 2.1.4 Java 1.4.2 and a database containing French and German diacritics, and I have had no problem at all. I originally used PostgreSQL 7.3.3 and made no change to the database when I upgraded. It may be significant that I used Marc Liyanage's PostgreSQL package (http://www.entropy.ch/software/macosx/) rather than compiling the thing myself. Regards Steve On 1 Apr 2004, at 14:24, Yves Vindevogel wrote: Sure, but ... it's not only OSX related. I had the same problem too on Linux (Slack 9.1) Seems to be a bug in Postgresql 7.4 (maybe) or my compilation of the driver (now checking) Anyway, I think it should be put under a topic "Cocoon, file encoding and database (jdbc) encoding" I'll create my piece of that document. No problem with that. On 01 Apr 2004, at 14:08, Jorg Heymans wrote: Thank god you finally solved it ! :) Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows that it was never really a cocoon related problem but it could go into a "how to get postgres and cocoon to play well together on MacOSX" section. Regards Jorg Yves Vindevogel wrote: I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: *From: *Peter Mount <[EMAIL PROTECTED]> *Date: *Thu 1 Apr 2004 11:25:54 CEST *To: *Yves Vindevogel <[EMAIL PROTECTED]> *Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) * Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgresql and the jdbc driver that causes it most. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Met vriendelijke groeten, Bien à vous, Kind regards, Yves Vindevogel Implements Mail: [EMAIL PROTECTED] - Mobile: +32 (478) 80 82 91 Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76 Markt 18c - 9700 Oudenaarde - Tel: +32 (55) 30 55 76 Web: http://www.implements.be First they ignore you. Then they laugh at you. Then they
Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
I'm glad Yves has found a work-around to his problem. However, I would like to point out that I am using the following together under Mac OS X 10.3.3: PostgreSQL 7.4 PG JDBC 7.3 Cocoon 2.1.4 Java 1.4.2 and a database containing French and German diacritics, and I have had no problem at all. I originally used PostgreSQL 7.3.3 and made no change to the database when I upgraded. It may be significant that I used Marc Liyanage's PostgreSQL package (http://www.entropy.ch/software/macosx/) rather than compiling the thing myself. Regards Steve On 1 Apr 2004, at 14:24, Yves Vindevogel wrote: Sure, but ... it's not only OSX related. I had the same problem too on Linux (Slack 9.1) Seems to be a bug in Postgresql 7.4 (maybe) or my compilation of the driver (now checking) Anyway, I think it should be put under a topic "Cocoon, file encoding and database (jdbc) encoding" I'll create my piece of that document. No problem with that. On 01 Apr 2004, at 14:08, Jorg Heymans wrote: Thank god you finally solved it ! :) Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows that it was never really a cocoon related problem but it could go into a "how to get postgres and cocoon to play well together on MacOSX" section. Regards Jorg Yves Vindevogel wrote: I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: *From: *Peter Mount <[EMAIL PROTECTED]> *Date: *Thu 1 Apr 2004 11:25:54 CEST *To: *Yves Vindevogel <[EMAIL PROTECTED]> *Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) * Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgresql and the jdbc driver that causes it most. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Met vriendelijke groeten, Bien à vous, Kind regards, Yves Vindevogel Implements Mail: [EMAIL PROTECTED] - Mobile: +32 (478) 80 82 91 Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76 Markt 18c - 9700 Oudenaarde - Tel: +32 (55) 30 55 76 Web: http://www.implements.be First they ignore you. Then they laugh at you. Then they fight you. Then you win. Mahatma Ghandi. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
Sure, but ... it's not only OSX related. I had the same problem too on Linux (Slack 9.1) Seems to be a bug in Postgresql 7.4 (maybe) or my compilation of the driver (now checking) Anyway, I think it should be put under a topic "Cocoon, file encoding and database (jdbc) encoding" I'll create my piece of that document. No problem with that. On 01 Apr 2004, at 14:08, Jorg Heymans wrote: Thank god you finally solved it ! :) Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows that it was never really a cocoon related problem but it could go into a "how to get postgres and cocoon to play well together on MacOSX" section. Regards Jorg Yves Vindevogel wrote: I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: *From: *Peter Mount <[EMAIL PROTECTED]> *Date: *Thu 1 Apr 2004 11:25:54 CEST *To: *Yves Vindevogel <[EMAIL PROTECTED]> *Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) * Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgresql and the jdbc driver that causes it most. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Met vriendelijke groeten, Bien à vous, Kind regards, Yves Vindevogel Implements Mail: [EMAIL PROTECTED] - Mobile: +32 (478) 80 82 91 Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76 Markt 18c - 9700 Oudenaarde - Tel: +32 (55) 30 55 76 Web: http://www.implements.be First they ignore you. Then they laugh at you. Then they fight you. Then you win. Mahatma Ghandi.
Re: Fwd: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
Thank god you finally solved it ! :) Seeing how much time you've spent on this (weeks AFAIK), could you wiki this up maybe? I know the end solution shows that it was never really a cocoon related problem but it could go into a "how to get postgres and cocoon to play well together on MacOSX" section. Regards Jorg Yves Vindevogel wrote: I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: *From: *Peter Mount <[EMAIL PROTECTED]> *Date: *Thu 1 Apr 2004 11:25:54 CEST *To: *Yves Vindevogel <[EMAIL PROTECTED]> *Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) * Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgresql and the jdbc driver that causes it most. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) - WAS Encoding problem on OSX
I mailed with Peter Mount regarding the Encoding problem on OSX. I found out this Peter sent me his .jar from version 7.2. I recompiled my database and did initdb again, this time with --encoding=latin1 I used his jar, and tested with some dburls. The one that works is with ?charSet=UTF8 And then, all of a suddenly, it works !!! I see no real logic in it, but after searching a couple of weeks, I'm happy that it works. I mailed Peter to find out why my jar is not working. Hope to hear from him soon. This may be a bit off topic now, but I'd like to inform Alex and others that I did find a solution. My tests with UTF8 proved vital, maybe they can do that too. Begin forwarded message: From: Peter Mount <[EMAIL PROTECTED]> Date: Thu 1 Apr 2004 11:25:54 CEST To: Yves Vindevogel <[EMAIL PROTECTED]> Subject: Re: (* - BIG - *) problem with Postgresql JDBC (related to Cocoon) Yves Vindevogel wrote: Hi Peter, Thanks for the quick answer. I installed a Java SQL client called SQL4J. It's just a graphical thing around some JDBC drivers to do queries. The problem occurs there too, so it's not Cocoon related. Last night, I recompiled my postgresql with ./configure options: --with-java --with-perl --with-python --with-tcl --without-readline --without-tk and --with-multibyte (I saw this was a configure option in version 7.2 or 7.1, which is no longer used or no longer documented at least) I did my initdb with ./initdb -D mydir --encoding=latin1 and locale=us_en (or en_us) I created my testdb also with the --encoding=latin1 That should help, right ? This is the way I do my encoding of the database ? Yes, although all that was needed was the createdb with --encoding=latin1. Adding that to initdb simply makes it the default for createdb. And for the jdbc url, I can simply use ?charSet=latin1 Try it without ?charSet=latin1 and see what happens. I don't use it here (while my db's are latin1), so that may be part of the problem. The db is sending it ok, but then because of that parameter, the jdbc driver is then trying to translate it again. Could there be a conjunction with the Java VM ? I had this database running in version 7.3 and I had a problem connecting from one machine. That was a machine with all the latest software on it, including JVM 1.4.2_03. "Old" installations didn't have that problem. I find that the JVM version doesn't really matter. Usually with connection problems, its the version of postgresql and the jdbc driver that causes it most. Peter
