Re: Policy on pulling in code from other projects?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Policy on pulling in code from other projects?
Date: 2011-07-22 17:26:44
Message-ID: 4E29B2D4.5000902@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/22/2011 09:03 AM, Robert Haas wrote:
> On Fri, Jul 22, 2011 at 11:43 AM, Joshua D. Drake<jd(at)commandprompt(dot)com> wrote:
>> OP of this thread:
>>
>> http://archives.postgresql.org/pgsql-hackers/2011-07/msg01144.php
>>
>> It is letting pgsql use URI syntax.
>
> Sorry, I missed that the first time.
>
> IMHO, it seems like it would be simpler to do that by rolling our own
> code rather than importing someone else's.

I guess it would depend on how full featured we want the code. The
library provides validation of various things that rolling our own code
likely wouldn't. I mean, it is a library just like libssl or any other
such thing.

I would imagine that rolling our own code would likely be simpler but
the code itself would be dumber (not bad, just not as capable) and we
would be duplicating the effort of an already established project. Do we
really want to do that?

Sincerely,

Joshua D. Drake

>

--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2011-07-22 17:34:39 Re: pg_class.relistemp
Previous Message Robert Haas 2011-07-22 16:45:39 Re: Questions and experiences writing a Foreign Data Wrapper