|
From: Joseph T. <dra...@gm...> - 2004-11-01 01:48:36
|
On Sun, 31 Oct 2004 12:04:44 +0100 (CET), Garvin Hicking
<squ...@su...> wrote:
> Hi Joseph!
>
> > -CREATE {FULLTEXT} INDEX entry_idx on {PREFIX}entries (title,body,extended);
> > +#Creating an index on the body and extended body is a bad idea
> > +CREATE {FULLTEXT} INDEX entry_idx on {PREFIX}entries (title);
> > CREATE INDEX date_idx ON {PREFIX}entries (timestamp);
> > CREATE INDEX mod_idx ON {PREFIX}entries (last_modified);
>
> This breaks the fulltext search. Please revert at least for MySQL, don't know
> how fulltext search works for PostgreSQL.
>
> Can't PostgreSQL create a bigger index? That sucks! :-)
>
> Regards,
> Garvin.
I think this introduces our very first irreparable shift. Unless we
can figure out a way to keep fulltext searching working on MySQL and
to allow more than 4000 characters in a blog entry on PostgreSQL we'll
need to split the SQL into two files, at least for the indices.
BTW, in what way does this "break" full text searching. It *should*
only make them slower as there's no index to reference when searching.
I guess I haven't a clue about how that works.
--
Joseph Tate
Personal e-mail: jtate AT dragonstrider DOT com
Web: http://www.dragonstrider.com
|
