Re: Policy on pulling in code from other projects?

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Policy on pulling in code from other projects?
Дата
Msg-id CA+TgmobS+-SsML5Ym6oN0zBcfL+T_=RciARf=cfgRKvuC+1dNQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Policy on pulling in code from other projects?  ("Joshua D. Drake" <jd@commandprompt.com>)
Ответы Re: Policy on pulling in code from other projects?
Список pgsql-hackers
On Fri, Jul 22, 2011 at 10:51 AM, Joshua D. Drake <jd@commandprompt.com> 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.
>
> 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Hitoshi Harada
Дата:
Сообщение: Re: Parameterized aggregate subquery (was: Pull up aggregate subquery)
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Tracing in Postgres