frank_lupo wrote:
> Hi all,
>
> I have create database èèèè not "èèèè".
> When I click on dabatabase èèèè in tree pgadmin3 show error: database "____"
> does not exist
Uuu, this was a really bad one.
The name of the database as displayed depends on the encoding used when
the database was created, and the database used when retrieving the
database information. Unfortunately, we can't know this at connect time,
so we have to guess.
In your case, you obviously created the database over a Unicode
connection, so it's stored as "èèèè". If you do SELECT * from
pg_database on a Unicode connection again, you'll get "èèèè", a
SQL_ASCII connection (usually template1) you see that encoded string.
While connecting, we only tried without Unicode conversion. I've added a
second try now.
Additionally, the name may be even unreadable. This can happen if you
create the database using SQL_ASCII (even if the DB itself is UNICODE).
In that case, it's impossible to retrieve the pg_database row, because
its content is illegal for unicode.
cvs patch committed, new snapshot to come.
Regards,
Andreas
