From: | "Nikolay Samokhvalov" <samokhvalov(at)gmail(dot)com> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Modifying and solidifying contrib |
Date: | 2007-02-07 18:15:42 |
Message-ID: | e431ff4c0702071015p299994e5n4383b87ffd854518@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/7/07, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Nikolay Samokhvalov wrote:
> >
> > I still do not understand why is it so needed.
> > Your argument is "some apps aren't able to call functions as
> > schemaname.functionname(arg1, arg2, ..)", right?
>
> wrong.
>
> >
> > I still think that separate namespaces for extensions is a good idea
> > while adjusting search_path is not. I've explained my POV in details
> > several messages ago in this thread...
>
>
> The difference between us is that I am less inclined to be prescriptive
> about such matters than you are. I think that as namespace use expands
> we should also probably provide better support for adding things to the
> search path (or indeed taking things away). If you don't want to use it
> then don't, but I don't see why you are so insistent on denying such
> facilities to others.
ok, looks like I've misunderstood your mesages. Sorry for that. Surely
additional capabilities for manipulation with search_path cannot
hinder anybody.
--
Best regards,
Nikolay
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-02-07 18:43:10 | Re: Proposal: TABLE functions |
Previous Message | Markus Schiltknecht | 2007-02-07 17:54:56 | Re: Proposal: Commit timestamp |