Replace current search solution #232

Closed
opened 2026-02-04 17:49:54 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @ssddanbrown on GitHub (Jan 14, 2017).

https://github.com/teamtnt/tntsearch
https://github.com/teamtnt/laravel-scout-tntsearch-driver

Advantages

  • Will remove MySQL5.6+ requirement (And thus possibly make it easier to support other DB's in the future).
  • Seems to be simple and fast - Need to investigate
  • Could help to avoid odd issues seen using MySQL fulltext searches (#269) and prevent having to resort to 'LIKE' queries - Need to investigate

Issues

  • Need to look how to integrate with permissions system.
  • Will be an extra dependency and will introduce SQLite requirement.
Originally created by @ssddanbrown on GitHub (Jan 14, 2017). https://github.com/teamtnt/tntsearch https://github.com/teamtnt/laravel-scout-tntsearch-driver ### Advantages * Will remove MySQL5.6+ requirement (And thus possibly make it easier to support other DB's in the future). * Seems to be simple and fast - *Need to investigate* * Could help to avoid odd issues seen using MySQL fulltext searches (#269) and prevent having to resort to 'LIKE' queries - *Need to investigate* ### Issues * Need to look how to integrate with permissions system. * Will be an extra dependency and will introduce SQLite requirement.
OVERLORD added the 🛠️ Enhancement🔧 Maintenance Open to discussion labels 2026-02-04 17:49:54 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Feb 27, 2017):

Looks like integrating TNTsearch will be a lot of hassle when combined with the permissions system. Ideally we'd have something that lives in MySQL so we can easily join permissions as required.

Maybe a simple custom MySQL table? Upon update, break pages down into terms and score on frequency and importance (Dependant on field). Then we can use "LIKE 'abc%' matching at a term level which will still use indexes.

@ssddanbrown commented on GitHub (Feb 27, 2017): Looks like integrating TNTsearch will be a lot of hassle when combined with the permissions system. Ideally we'd have something that lives in MySQL so we can easily join permissions as required. Maybe a simple custom MySQL table? Upon update, break pages down into terms and score on frequency and importance (Dependant on field). Then we can use "LIKE 'abc%' matching at a term level which will still use indexes.
Author
Owner

@muramasatheninja commented on GitHub (Mar 8, 2017):

Could Sphinx be an option?
http://sphinxsearch.com/

@muramasatheninja commented on GitHub (Mar 8, 2017): Could Sphinx be an option? http://sphinxsearch.com/
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#232