Re: [JDBC] ? (question mark) characters

2001-09-03 Thread Rene Pijlman
On 02 Sep 2001 03:35:29 +0200, you wrote: You don't need multibyte for iso-8859-1. That's what I thought. But with current CVS (7.2) creating a database with -E LATIN1 fails without multibyte support. See the link in one of my previous postings in this thread. Regards, René Pijlman [EMAIL

Re: [JDBC] ? (question mark) characters

2001-09-01 Thread Rene Pijlman
On Thu, 30 Aug 2001 11:06:13 -0300, you wrote: Thank you all for your help: Dia Thursday, 30 de August, 2001 10:42, Rene Pijlman wrote: like áéíóú (aeiou with accent)... they are replaced by question marks (?)... any ideas? What's the character encoding of the database? It doesn't matter.

Re: [JDBC] ? (question mark) characters

2001-09-01 Thread Gunnar Rønning
* Rene Pijlman [EMAIL PROTECTED] wrote: | | Have you tried it with a database which was created with -E | LATIN1 and with an installation configured with | --enable-multibyte? You don't need multibyte for iso-8859-1. A simple test case reproducing the problem would be nice though. I don't have

[JDBC] ? (question mark) characters

2001-08-30 Thread Ricardo Pardini
Ok, I tried all the drivers currently available at http://jdbc.fastcrypt.com. They all seem to correct the problem with long (8k) SQL statements, but they're all broken considering Portuguese characters like áéíóú (aeiou with accent)... they are replaced by question marks (?)... any ideas?

RE: [JDBC] ? (question mark) characters

2001-08-30 Thread Rene Pijlman
Ricardo Pardini wrote: they're all broken considering Portuguese characters like áéíóú (aeiou with accent)... they are replaced by question marks (?)... any ideas? What's the character encoding of the database? See http://postgresql.demunnikservices.nl/users-lounge/docs/7.1/admi

Re: [JDBC] ? (question mark) characters

2001-08-30 Thread Ricardo Pardini
Thank you all for your help: Dia Thursday, 30 de August, 2001 10:42, Rene Pijlman wrote: like áéíóú (aeiou with accent)... they are replaced by question marks (?)... any ideas? What's the character encoding of the database? It doesn't matter. I have tried it with SQL_ASCII, ISO-8859-1,