3 ms·
The amount of informations around is surprisingly poor; it's hard to find technical information. At least a significant difference is MariadDB's addition of se
by pizza234 5y ago
The amount of informations around is surprisingly poor; it's hard to find technical information.
At least a significant difference is MariadDB's addition of several specialized engines - see https://mariadb.com/kb/en/storage-engines https://mariadb.com/kb/en/storage-engines:
- MariaDB ColumnStore: Column-based
- Mroonga: Full text search
- OQGRAPH: Graph storage
- SphinxSE: Full text search
Where the above use cases are required, it's actually a big deal. A common use case may be FT searches - MySQL's support is a trainwreck, and I have the suspicion that Oracle has little to no interest in it.
- tehbeard 5y agoCurious to learn more about Mroonga. FT has been a sticking point for several sites we've built, and the search daemons (typesense, meilisearch) tend to not as accurate as we'd like.
- sroussey 5y agoSame. I’ll have to take a look as well. The built-in FT going back to MyISAM and later was ok for small things, but needed to remain in memory wand dint handle lots of updates well. At one point we split a table into shards on the same database to ease locking issues. One thing I wish were available was a hybrid btree and inverted index. If you are multi tenant then you want your search to only happen within the one user’s data — not across all accounts and then filter for the one user.