It makes no sense to make a fulltext on the data column in the mimeparts
table, because most of the data is base64 encoded and/or is a attachment..
We may need a second table that only holds the (decoded) message part
(text/plain html/plain (maybe with removed html)). This table could have a
mysql/postgre fulltext column.
Alternative based on this table we can create our own fulltext engine.
But the thing that makes much more sense is to use an external search
engine like Sphinx or lucene or what ever.
Some nice SE Answers
http://stackoverflow.com/questions/737275/comparison-of-full-text-search-engine-lucene-sphinx-postgresql-mysql
Anyway it should be optional.
I also have a question is it possible to deactivate imaps search? because
if a query runs multiple minutes its highly possible that multiple people
starts a search and may kill the server?!
Am .03.2015, 11:58 Uhr, schrieb Thomas Raschbacher <lord...@lordvan.com>:
Am 06.03.2015 um 10:11 schrieb Andrea Brancatelli:
There's already some Oracle-specific code in the codebase, it's, just
one query, it could be implemented with a specific code for Full Text
capable/not capable DBMS.
I don't have a problme with it myself ^^ someone just has to maintain
the code then .. btw afaik LIKE BINARY is mysql specific anyway (at
least postgres doesn't know that)
Regards
--
Harald Leithner
ITronic
Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria
Tel: +43-1-545 0 604
Fax: +43-1-786 23 88 26
Mobil: +43-699-123 78 4 78
Mail: leith...@itronic.at | itronic.at
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
