Re: text search vs schemas - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: text search vs schemas
Date
Msg-id 87fy2iu5vt.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: text search vs schemas  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: text search vs schemas  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> "Trevor Talbot" <quension@gmail.com> writes:
>> Wouldn't treating them as actual objects remove this whole issue?
>
> Uh, no.  Function names for example are subject to search-path
> confusion.

Wait, are they? They are in PL languages but only because most languages store
their source code as text just as is happening here. 

But they're not in views or other native SQL uses of functions because they
store the reference to the specific function's OID. In dumps they output the
schema along with the name. As in:

postgres=# \d foo.testv      View "foo.testv"Column |  Type   | Modifiers 
--------+---------+-----------i      | integer | a      | integer | 
View definition:SELECT test.i, foo.a(test.i) AS a  FROM foo.test;

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: text search vs schemas
Next
From: Oleg Bartunov
Date:
Subject: Re: text search vs schemas