Re: Primary schema name prepended to database objects

You are right. Silly me. The qualification was in _my_ code.

I definitely need to slow down a bit :-) .

Peter

Kris Jurka wrote:
>
> 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
>