From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
---|---|
To: | IPN Bala GSS TVL <ipnb87(at)gmail(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Error with Database name |
Date: | 2015-05-19 16:40:28 |
Message-ID: | CAFNqd5X3QOmBkRJemyhcmvX-zusma7dGdP2bU5qAs3mYkSQz4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 19 May 2015 at 10:57, IPN Bala GSS TVL <ipnb87(at)gmail(dot)com> wrote:
>
> Hi Postgres team,
> Today we faced an issue with database name. Screenshot is attached.
>
> The error is,
> 2015-05-19 11:13:14
> CON\0000000147 Query execution failed :
> Npgsql.NpgsqlException:
> database "DDV_TDB_02_S2" does not exist
> Severity: FATAL
It seems likely to me that the issue here is that the database name
contains some Unicode value that looks like whitespace.
A clue is pretty clear in the pane that shows a CREATE DATABASE command
where the name of the database contains a couple of extra characters; the
name can't be "DDV_TDB_02_S2", as you can see "DDV_TDB_02US_S2" in the
pane. I don't know what the "US" bit is; presumably it is some Unicode
character or characters that do not display elsewhere.
This does not appear to be a bug in PostgreSQL, hence not something that
anybody in the community ought to need to fix.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"
From | Date | Subject | |
---|---|---|---|
Next Message | cpburnz | 2015-05-19 17:26:19 | BUG #13317: Cannot select multiple columns from multiple rows returned from PL/Python function |
Previous Message | IPN Bala GSS TVL | 2015-05-19 14:57:31 | Error with Database name |