Re: Primary schema name prepended to database objects

Поиск
Список
Период
Сортировка
От Kris Jurka
Тема Re: Primary schema name prepended to database objects
Дата
Msg-id Pine.BSO.4.56.0502021445470.7681@leary.csoft.net
обсуждение исходный текст
Ответ на Re: Primary schema name prepended to database objects  (Kovács Péter <pkovacs@chemaxon.hu>)
Ответы Re: Primary schema name prepended to database objects  (Kovács Péter <peter.kovacs@chemaxon.hu>)
Список pgsql-jdbc

On Wed, 2 Feb 2005, [ISO-8859-1] Kov�cs P�ter wrote:

> The problem is that where I write in my code, say:
>
> "SELECT * FROM mytable"
>
> the backend log contains:
>
> "SELECT * FROM myusername.mytable"
>
> Someone along the way (I suspect the JDBC driver, but I am not sure)
> "qualifies" my database objects. Probably that is why the "public"
> schema is not searched for "mytable".
>

This is definitely not the JDBC driver doig this.  The qualification by
search_path I mentioned is done on the server and is done behind the
scenes, meaning the qualified name would not show up in the backend log
because it does not rewrite your original query.  The fact that the
backend log says mysername.mytable is a strong indication that it is in
fact your software that is doing this because neither the driver, nor the
server would do such a thing.  Some kind of reproducible test case would
convince me otherwise, but I don't expect to be receiving one.

Kris Jurka

В списке pgsql-jdbc по дате отправления:

Предыдущее
От: Kovács Péter
Дата:
Сообщение: Re: Primary schema name prepended to database objects
Следующее
От: Kris Jurka
Дата:
Сообщение: Re: Patch: implement login timeout support