[wp-trac] [WordPress Trac] #51769: Full-text search support

[WordPress Trac]

#51769: Full-text search support
--------------------------------------+------------------------------
 Reporter:  zieladam                  |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Database                  |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  dev-feedback 2nd-opinion  |     Focuses:
--------------------------------------+------------------------------
Changes (by azaozz):

 * keywords:  dev-feedback has-patch => dev-feedback 2nd-opinion


Comment:

 Looking here again, there may be couple more considerations:
 1. Speed consideration for when saving to the DB. If there's a fulltext
 index on `post_content`, it will have to be updated every time a new post
 is saved or a post is updated. Normally that should be quite fast, but
 might become problematic for very big sites with millions of rows in
 `wp_posts` where the index will be several MB (saving a post is quite slow
 afaik). Perhaps worth a look/test.
 2. Disk space: how much bigger the DB will be with a fulltext index on
 post_content?

 If the above two are of no concern, perhaps the fulltext indexes can be
 added only on new installs (when supported)? Then the search queries can
 use fulltext if it exists, something like: `SHOW INDEX FROM my_table WHERE
 Key_name = 'index_to_check'`.

 > the import will fail as FULLTEXT KEY will be part of CREATE TABLE and
 not a separate ALTER TABLE statement

 Yeah, thinking good docs would be sufficient for this case. Something like
 "When importing to older versions of MySQL, and the import fails with
 ...... error message, drop the fulltext indexes before exporting and try
 again".

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51769#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform