Re: Question about character encoding - Mailing list pgsql-cygwin

From Markus Wollny
Subject Re: Question about character encoding
Date
Msg-id 2266D0630E43BB4290742247C8910575014CE13F@dozer.computec.de
Whole thread Raw
In response to Question about character encoding  ("Markus Wollny" <Markus.Wollny@computec.de>)
List pgsql-cygwin
Jean-Michel POURE [mailto:jm.poure@freesurf.fr] wrote:

> SQL_ASCII encoding can handle most european languages, including
German. So,
> just create a database with SQL_ASCII encoding. And this will solve
your
> problem.


Thanks - that did it. I just didn't think ASCII was the correct encoding
as one usually relates ascii to one-byte standard characters.

One more question though: It's actually possible to create databases
with names in capital letters using PGAdmin II. As it's impossible to
drop databases in PGAdmin, I tried to do it via pgsql. It seems however,
that psql just automatically converts anything to lower case, therefore
giving me "ERROR: DROP DATABASE: database "test" does not exist" when I
try "drop database TEST;".
When doing "select * from pg_database;" on template1 "TEST" is sitting
there, glaring, without me being able to kick it. Therefore I have the
impression that it's absolutely not advisable to create any object with
capitals in it's name via PG Admin II. Is that correct? If so, why not
automatically convert any names in the connect string to lower case, in
order to prevent this from happening? Would there be still some way of
dropping such a database even though it's not possible with neither PG
Admin II nor psql?

Cheers & thanks for your support,

    Markus

pgsql-cygwin by date:

Previous
From: Dave Page
Date:
Subject: Re: Question about character encoding
Next
From: Dave Page
Date:
Subject: Re: Question about character encoding