| From: | Tony Grant <tony(at)animaproductions(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
| Date: | 2001-05-04 16:29:57 |
| Message-ID: | 988993797.1582.4.camel@tonux |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On 04 May 2001 11:40:48 -0400, Tom Lane wrote:
>
> But a non-MULTIBYTE backend doesn't even have the concept of "setting
> the encoding" --- it will always just report SQL_ASCII.
What kind of error message does "createdb -E LATIN1" give on a non
MULTIBYTE backend?
Maybe there needs to be a note somewhere informing people from Europe
that they too need MULTIBYTE as an option at compile time. i.e. In a
bright yellow box in the HTML docs...
And in the Reference manual and man pages the -E option for createdb
needs a note to specify that it applies to MULTIBYTE backends only.
Cheers
Tony Grant
--
RedHat Linux on Sony Vaio C1XD/S
http://www.animaproductions.com/linux2.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Burton | 2001-05-04 16:36:18 | Re: Metaphone function attachment |
| Previous Message | Fabrice Scemama | 2001-05-04 16:21:19 | Re: Postgresql.exe 7.1 for M$ OS |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-04 16:40:26 | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
| Previous Message | Tony Grant | 2001-05-04 15:58:41 | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |