Skip site navigation (1) Skip section navigation (2)

Re: search_path vs extensions

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)enterprisedb(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Subject: Re: search_path vs extensions
Date: 2009-05-29 16:22:03
Message-ID: 6A47AF24-4C11-4D7B-A44C-0D414AC5FAAF@kineticode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On May 29, 2009, at 3:24 AM, Peter Eisentraut wrote:

> Yeah, to reiterate what I posted elsewhere, perhaps it'd be a good  
> idea to
> give up on the search path idea altogether and think more in terms  
> of an
> import facility like Python, Java, and sometimes Perl have.

+1

Actually, Perl's is usually a file path. `use Foo::Bar::Baz;` triggers  
a search for Foo/Bar/Baz.pm unless Foo::Bar::Baz is already loaded.

Best,

David

In response to

pgsql-hackers by date

Next:From: David E. WheelerDate: 2009-05-29 16:23:26
Subject: Re: search_path vs extensions
Previous:From: Tom LaneDate: 2009-05-29 16:17:44
Subject: Re: Compiler warning cleanup - unitilized const variables, pointer type mismatch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group