On Wed, 24 Oct 2007 18:19:37 -0700
"Chris Travers" <[EMAIL PROTECTED]> wrote:
> Hi all;
>
> I am wondering what everyone thinks we should do about full text
> search, PostgreSQL 1.3, and tsearch2.PostgreSQL 8.3 will be
> changing a lot of the full text search interface. Personally I want
> t
Chris Travers wrote:
> One final option we might have is to simply refuse to support
> PostgreSQL 8.3 in LSMB1.3 and apply one of the above fixes for 1.4.
>
> Thoughts, suggestions, etc?
>
> Best Wishes,
> Chris Travers
How about documenting the changes needed in order to run on 8.3 and
leave i
Hi all;
I am wondering what everyone thinks we should do about full text
search, PostgreSQL 1.3, and tsearch2.PostgreSQL 8.3 will be
changing a lot of the full text search interface. Personally I want
to stay as far away from maintaining multiple schemas as possible
because this is a recipe f
On 10/24/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> On Wed, 24 Oct 2007 09:51:07 +0100
> MJ Ray <[EMAIL PROTECTED]> wrote:
>
>
> > > CC would have the advantage of being the most popular non-code set
> > > of licenses, and thus help us on license compatibility more than
> > > any other.
> >
>
On Wed, 24 Oct 2007 09:51:07 +0100
MJ Ray <[EMAIL PROTECTED]> wrote:
> > CC would have the advantage of being the most popular non-code set
> > of licenses, and thus help us on license compatibility more than
> > any other.
>
> How? Many CC licences are mutually incompatible and the most popula
Josh Berkus <[EMAIL PROTECTED]> wrote:
> MJ,
> > Creative Commons licenses are complicated and contain lawyerbombs -
> > things which are vague and/or confusing and/or CC has ignored requests
> > to explain. I don't see the benefit over a BSD-style documentation
> > licence if that's what's wanted
