Re: Policy on pulling in code from other projects?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Policy on pulling in code from other projects?
Date: 2011-07-22 15:36:30
Message-ID: CA+TgmobS+-SsML5Ym6oN0zBcfL+T_=RciARf=cfgRKvuC+1dNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 22, 2011 at 10:51 AM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> On 07/21/2011 11:13 AM, Tom Lane wrote:
>>
>> "Joshua D. Drake"<jd(at)commandprompt(dot)com>  writes:
>>>
>>> So I am looking intently on what it is going to take to get the URI
>>> patch done for psql [1] and was digging around the web and have a URI
>>> parser library. It is under the New BSD license and is strictly RFC  RFC
>>> 3986 [2] compliant .
>>
>> Surely we do not need a whole library to parse URIs.
>
> Any other comments? I don't want to do a bunch of work just to have it
> tossesd on a technicality.

Well, you haven't explained what feature you are trying to develop, so
it's a bit premature to speculate on whether that feature is valuable
enough to justify the carrying cost of another library.

Like Tom, I'm not real sure why we would need a library for this. It
seems like a hundred lines of C would be sufficient for most things
you'd likely want to do, and less work than integrating someone else's
code.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-07-22 15:38:22 Re: Tracing in Postgres
Previous Message Hitoshi Harada 2011-07-22 15:35:40 Re: Parameterized aggregate subquery (was: Pull up aggregate subquery)