Re: View definition and schema search path bug or expected behaviour?

From: Chris Bartlett <c(dot)bartlett(at)paradise(dot)net(dot)nz>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: View definition and schema search path bug or expected behaviour?
Date: 2012-07-26 02:47:29
Message-ID: p06240807cc365f416396@[192.168.200.4]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

At 7:37 PM -0700 25/7/12, Adrian Klaver wrote:
>I am guessing if you do show search_path; from psql you will see
>that the public schema is before the bob schema. The SELECT for the
>unqualified people table in CREATE VIEW bob.people_view will find
>public.people first in that case.

I don't think that's it:

show search_path
-> "$user",public

select SESSION_USER
-> bob

From the docs:
"The value for search_path must be a comma-separated list of schema
names. If one of the list items is the special value $user, then the
schema having the name returned by SESSION_USER is substituted, if
there is such a schema. (If not, $user is ignored.)"

Also:
select * from people
-> returns records from bob.people

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2012-07-26 02:51:30 Re: View definition and schema search path bug or expected behaviour?
Previous Message Adrian Klaver 2012-07-26 02:37:56 Re: View definition and schema search path bug or expected behaviour?