Re: Policy on pulling in code from other projects? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Policy on pulling in code from other projects?
Date
Msg-id 4E2AA4CE.8000005@dunslane.net
Whole thread Raw
In response to Re: Policy on pulling in code from other projects?  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Policy on pulling in code from other projects?
Re: Policy on pulling in code from other projects?
List pgsql-hackers

On 07/22/2011 10:51 AM, Joshua D. Drake wrote:
> On 07/21/2011 11:13 AM, Tom Lane wrote:
>> "Joshua D. Drake"<jd@commandprompt.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.
>>
>>             regards, tom lane
>>
>
> Any other comments? I don't want to do a bunch of work just to have it 
> tossesd on a technicality.
>
>

1. I think the proposed use is of very marginal value at best, and 
certainly not worth importing an external library for.

2. Even if we have the feature, we do not need to parse URIs generally. 
A small amount of hand written C code should suffice. If it doesn't that 
would itself be an argument against it.

cheers

andrew



pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: cataloguing NOT NULL constraints
Next
From: Andrew Dunstan
Date:
Subject: Re: Questions and experiences writing a Foreign Data Wrapper