pgmonitor

i want to list non-system tables with psql and get the following error. any
alternatives? Thanks.

EPost-# \dt
ERROR: invalid byte sequence for encoding "UNICODE": 0xed

my database used UNICODE as the encoding. and the OS is win2k pro wich
simplified chinese
as default language.

Am Montag, den 01.08.2005, 16:19 -0600 schrieb YL:

i want to list non-system tables with psql and get the following error. any
alternatives? Thanks.

EPost-# \dt
ERROR: invalid byte sequence for encoding "UNICODE": 0xed

my database used UNICODE as the encoding. and the OS is win2k pro wich
simplified chinese
as default language.

Dont steal threads by just answering to an unrelated e-mail
from the list!

To your question: afaic the win32 port currently has some issues
with the right support of unicode. You may check your documentation.
Do you think its a good idea to actually name objects in the database
in a foreign encoding? I'd stick to english language names here because
it makes chatting about problems/hints much more easy on mailinglists.

--
Tino Wildenhain <tino@wildenhain.de>

i want to list non-system tables with psql and get the following error.

any

alternatives? Thanks.

EPost-# \dt
ERROR: invalid byte sequence for encoding "UNICODE": 0xed

my database used UNICODE as the encoding. and the OS is win2k pro wich
simplified chinese
as default language.

There is a character (0xED) that doesn't seem to be Unicode compliant.
Maybe you have a tablename that uses another encoding or is simply fscked
up.

I had those problems with some German character, after switching to UTF8
encoding. I solved it with a pg_dump of the DB that I converted with iconv
to UTF and restored it into the cluster. I have no idea if iconv exists
for Microsoft OSes, but there should be alternatives to convert encoding
to UTF.

I use a database with UNIBASE encoding too. Writing strings in unicode
with german vovels does not work. We access the database via the ODBC
driver.

What kind of documentation do you mean with You may check your
documentation ?

Best regards,
Josef Springer

Tino Wildenhain wrote:

Am Montag, den 01.08.2005, 16:19 -0600 schrieb YL:

i want to list non-system tables with psql and get the following error. any
alternatives? Thanks.

EPost-# \dt
ERROR: invalid byte sequence for encoding "UNICODE": 0xed

my database used UNICODE as the encoding. and the OS is win2k pro wich
simplified chinese
as default language.

Dont steal threads by just answering to an unrelated e-mail
from the list!

To your question: afaic the win32 port currently has some issues
with the right support of unicode. You may check your documentation.
Do you think its a good idea to actually name objects in the database
in a foreign encoding? I'd stick to english language names here because
it makes chatting about problems/hints much more easy on mailinglists.

--

mit freundlichen Grüssen,
Josef Springer
(Geschäftsleitung)

<cid:part1.00070301.03090100@netscape.com> -- the software company --

Orlando-di-Lasso Str. 2
D-85640 Putzbrunn

Tel. ++49(0)89 600 6920
Fax ++49(0)89 600 69220
mailto Josef.Springer@joops.com <mailto:Josef.Springer@joops.com>
Website http://www.joops.com

See http://www.postgresql.org/docs/faqs.FAQ_windows.html#2.6.

//Magnus

Hi Magnus,

the docmentation does not realy help me !

Client: Win2k, german language settings, SET client_encoding TO 'UNICODE'
Server: Win2k, german language settings, database with UNICODE encoding

I use PostgreSQL via ODBC and want to write and read strings containing
vovels.

I have read in the mailing lists, using UNICODE for the database works
??!??.
I have tried all other/many encoding combinations for server and client
allready, but nothing works !

Magnus Hagander wrote:

See http://www.postgresql.org/docs/faqs.FAQ_windows.html#2.6.

//Magnus

-----Original Message-----
Sent: Tuesday, August 02, 2005 1:11 PM
To: pgsql-general@postgresql.org
Subject: Re: unicode error on win32 Was: Re: [GENERAL] pgmonitor

I use a database with UNIBASE encoding too. Writing strings
in unicode with german vovels does not work. We access the
database via the ODBC driver.

What kind of documentation do you mean with You may check
your documentation ?

Best regards,
Josef Springer

Tino Wildenhain wrote:

Am Montag, den 01.08.2005, 16:19 -0600 schrieb YL:

i want to list non-system tables with psql and
get the following error. any
alternatives? Thanks.

EPost-# \dt
ERROR: invalid byte sequence for encoding
"UNICODE": 0xed

my database used UNICODE as the encoding. and
the OS is win2k pro wich
simplified chinese
as default language.

Dont steal threads by just answering to an unrelated e-mail
from the list!

To your question: afaic the win32 port currently has some issues
with the right support of unicode. You may check your
documentation.
Do you think its a good idea to actually name objects
in the database
in a foreign encoding? I'd stick to english language
names here because
it makes chatting about problems/hints much more easy
on mailinglists.

--

mit freundlichen Grüssen,
Josef Springer
(Geschäftsleitung)

-- the software company --

Orlando-di-Lasso Str. 2
D-85640 Putzbrunn

Tel. ++49(0)89 600 6920
Fax ++49(0)89 600 69220
mailto Josef.Springer@joops.com
<mailto:Josef.Springer@joops.com>
Website http://www.joops.com

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

--

mit freundlichen Grüssen,
Josef Springer
(Geschäftsleitung)

<cid:part1.03020203.00070402@netscape.com> -- the software company --

Orlando-di-Lasso Str. 2
D-85640 Putzbrunn

Tel. ++49(0)89 600 6920
Fax ++49(0)89 600 69220
mailto Josef.Springer@joops.com <mailto:Josef.Springer@joops.com>
Website http://www.joops.com

Hi Magnus,

the docmentation does not realy help me !

Client: Win2k, german language settings, SET client_encoding
TO 'UNICODE'
Server: Win2k, german language settings, database with
UNICODE encoding

I use PostgreSQL via ODBC and want to write and read strings
containing vovels.

I have read in the mailing lists, using UNICODE for the
database works ??!??.
I have tried all other/many encoding combinations for server
and client allready, but nothing works !

For german, I would assume LATIN1 is the correct encoding. Somebody who
knows more about german can probably confirm that :-)

UNICODE just does not properly work on win32 servers ATM.

//Magnus

Mart���n Marqu���s wrote:

What happend with pgmonitor?

Uh, it is at:

http://gborg.postgresql.org/project/pgmonitor/projdisplay.php

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

El Lun 08 Ago 2005 18:29, Bruce Momjian escribió:

Martín Marqués wrote:

What happend with pgmonitor?

Uh, it is at:

http://gborg.postgresql.org/project/pgmonitor/projdisplay.php

Yes, I know, but it looks like unsupported, and with the last Debian update
from 7.4 to 8.0 it got uninstalled. Could it be because of the drop of Tk
support?

--
select 'mmarques' || '@' || 'unl.edu.ar' AS email;
---------------------------------------------------------
Martín Marqués | Programador, DBA
Centro de Telemática | Administrador
Universidad Nacional
del Litoral
---------------------------------------------------------