| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Modifying and solidifying contrib |
| Date: | 2007-01-29 21:29:35 |
| Message-ID: | 45BE673F.8060002@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Keep in mind all contrib loads into public, and I don't remember any
> namespace conflict issues in the past.
>
That is beside the point. Of course there haven't been conflicts -
precisely because a single group controls the whole lot. What I said was
that we should behave as sane third party extension authors would,
namely to use their own namespace to protect themselves from conflicts
with other unknown extensions. It's called setting a good example or
eating your own dog food.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-01-29 21:32:43 | Re: Modifying and solidifying contrib |
| Previous Message | Tom Lane | 2007-01-29 21:22:43 | Re: Modifying and solidifying contrib |