From: | Culley Harrelson <culleyharrelson(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | t-ishii(at)sra(dot)co(dot)jp |
Subject: | Fwd: Re: unicode in 7.1 |
Date: | 2001-09-11 03:12:48 |
Message-ID: | 5.1.0.14.0.20010910200955.009f1e00@pop.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
The was corrupted in the process of the upgrade.
Is there some way to tell what the configuration options were when it was
installed? I am assuming by API you mean how am I accessing Postgres? JDBC.
Culley
>X-Apparently-To: culleyharrelson(at)yahoo(dot)com via web9605; 10 Sep 2001
>18:19:26 -0700 (PDT)
>X-Track: 1: 40
>To: culleyharrelson(at)yahoo(dot)com
>Cc: pgsql-general(at)postgresql(dot)org
>Subject: Re: [GENERAL] unicode in 7.1
>X-Mailer: Mew version 1.94.2 on Emacs 20.7 / Mule 4.1
> =?iso-2022-jp?B?KBskQjAqGyhCKQ==?=
>Date: Tue, 11 Sep 2001 10:19:00 +0900
>From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
>X-Dispatcher: imput version 20000228(IM140)
>Lines: 9
>
> > my isp recently upgraded form postgreSQL 7.0 to 7.1. It went pretty well
> > but I just discovered that non-english characters are now in the database
> > as a question mark-- inserting non-english characters produces a ? as
> > well. Any idea what has gone wrong and what we need to do to fix this?
>
>Hard to tell without knowing what the configuration option was and
>what kind of API you are using...
>--
>Tatsuo Ishii
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Hunter Hillegas | 2001-09-11 03:43:04 | MacOS X Build Fails with 7.1.3 |
Previous Message | Randy Hall | 2001-09-11 02:41:57 | Re: How to make a REALLY FAST db server? |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroyuki Yatabe | 2001-09-11 03:52:56 | Proposals for jdbc.sgml(in 7.1.3 doc) |
Previous Message | Jeroen van Vianen | 2001-09-10 18:00:39 | Fix for broken JDBC's getColumn() (take 2) |