|
From: Garvin H. <squ...@su...> - 2004-11-01 11:28:30
|
Hi Joseph!
> 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.
Hm, if postgresql really sucks that much that it can't define indexes not
affecting the size of the indexed columns, then that's true. But I somehow can't
believe that there is no workaround? I'll try to look into finding a good way to
make an optional SQLite/MySQL statement which does not affect postgresql.
Something like
/*[CONDITIONAL:MYSQL,MYSQLI,SQLITE] CREATE {FULLTEXT} INDEX on ...*/
and then strip the comment characters if the conditionals are met. But it would
really suck to need to insert that into 0.7 at this stage :(
> 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.
It breaks it fully, because without fulltext keys, the fulltext search of mysql
does not work. Since I currently am busy, would someone please revert the
change? If users are upgrading to CVS, they are screwed...
Regards,
Garvin.
--
Garvin Hicking | Web-Entwickler | Make me happy:
www.supergarv.de | #ICQ 21392242 | http://wishes.garv.info/
|
