Re: Primary schema name prepended to database objects

From: Kris Jurka <books(at)ejurka(dot)com>
To: Kovács Péter <pkovacs(at)chemaxon(dot)hu>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Primary schema name prepended to database objects
Date: 2005-02-02 19:50:03
Message-ID: Pine.BSO.4.56.0502021445470.7681@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Wed, 2 Feb 2005, [ISO-8859-1] Kovcs Pter 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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2005-02-02 20:36:14 Re: Patch: implement login timeout support
Previous Message Barry Lind 2005-02-02 17:32:01 Re: Patch: implement login timeout support