--- title: Manticore Speaks MySQL — So I Made It a Laravel Database... description: A Laravel database driver for Manticore Search that leverages Manticore's MySQL wire protocol compatibility to expose it as a first-class Eloquent connection.... canonical: https://daily.dev/posts/manticore-speaks-mysql-so-i-made-it-a-laravel-database-driver-instead-of-a-scout-engine-ttlilubi5 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Manticore Speaks MySQL — So I Made It a Laravel Database Driver Instead of a Scout Engine | daily.dev og:description: A Laravel database driver for Manticore Search that leverages Manticore's MySQL wire protocol compatibility to expose it as a first-class Eloquent connection.... og:url: https://daily.dev/posts/manticore-speaks-mysql-so-i-made-it-a-laravel-database-driver-instead-of-a-scout-engine-ttlilubi5 og:image: https://api.daily.dev/og/posts/tTlIlubi5.png og:image:alt: Manticore Speaks MySQL — So I Made It a Laravel Database Driver Instead of a Scout Engine og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Manticore Speaks MySQL — So I Made It a Laravel Database Driver Instead of a Scout Engine **[Medium](https://daily.dev/sources/medium_js)** · 6 min read · 0 upvotes · 0 comments ## Summary A Laravel database driver for Manticore Search that leverages Manticore's MySQL wire protocol compatibility to expose it as a first-class Eloquent connection. Instead of wrapping Manticore's HTTP/JSON API or using Laravel Scout, the package registers Manticore as a custom database connection with a grammar that handles dialect quirks. This gives developers full Eloquent features — models, migrations, query builder, pagination, casts — against a search engine. The package supports Manticore-specific features like MATCH() full-text search, KNN vector search, facets, highlights, and MVA columns via schema migrations. It runs in production for a compliance screening service. Known limitations include no transactions, partial UPDATE support for text fields, limited JOINs, and emulated PDO prepares. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I use Laravel Eloquent directly with Manticore Search instead of Laravel Scout? Manticore Search accepts MySQL wire protocol connections on port 9306, so a custom Laravel database driver with a dialect-specific grammar can register it as a first-class Eloquent connection. The laravel-manticore-eloquent package does this, giving models, migrations, pagination, casts, and chunking directly on Manticore instead of the limited search() call Scout exposes. _Developers weighing Scout against a native driver for Manticore can compare real tradeoffs surfaced on daily.dev._ ### Can I do KNN vector search using Laravel's query builder without a separate vector database? Yes, Manticore supports native KNN search, and because the Eloquent driver compiles builder calls straight into Manticore SQL, a knn() method plugs into the same query builder used for regular queries. It can be combined with selectRaw for knn_dist(), pagination, and casts, removing the need for a separate vector database in the stack. _Anyone consolidating vector search into an existing stack can track real-world approaches like this on daily.dev._ ### What are the limitations of using Manticore Search as if it were a MySQL database in Laravel? Manticore lacks transactions and row locks, so lockForUpdate() is a no-op and DB::transaction() semantics don't apply. UPDATE only modifies non-text attribute columns, requiring REPLACE INTO to rewrite text fields. Manticore owns document ids, so migrations skip any declared id column. Cross-index JOINs are restricted, and the driver forces PDO emulated prepares since server-side prepared statement support is limited. _Teams evaluating Manticore for production search workloads can weigh these gotchas via coverage on daily.dev._ ## Similar posts on daily.dev - [Manticore Search 25.0.0](https://daily.dev/posts/manticore-search-25-0-0-xaked8brj) · Manticore · 0 upvotes · 0 comments - [Laravel 13 now supports MariaDB Vector natively](https://daily.dev/posts/laravel-13-now-supports-mariadb-vector-natively-moxv4b4ls) · MariaDB.org · 3 upvotes · 0 comments - [Manticore Search 27.1.5: Authentication, sharded tables, conversational search and faster vector search](https://daily.dev/posts/manticore-search-27-1-5-authentication-sharded-tables-conversational-search-and-faster-vector-sea-vaeuj65j7) · Manticore · 2 upvotes · 0 comments - [Laravel ClickHouse: A Full-Featured ClickHouse Driver for Laravel](https://daily.dev/posts/laravel-clickhouse-a-full-featured-clickhouse-driver-for-laravel-dqro9rm9u) · Laravel News · 26 upvotes · 0 comments - [Meilisearch vs. Manticore: Use cases, features, & more](https://daily.dev/posts/meilisearch-vs-manticore-use-cases-features-more-8neujurkr) · Meilisearch · 0 upvotes · 0 comments --- Tags: [#php](https://daily.dev/tags/php), [#laravel](https://daily.dev/tags/laravel), [#full-text-search](https://daily.dev/tags/full-text-search), [#manticore-search](https://daily.dev/tags/manticore-search) [View this post on daily.dev](https://daily.dev/posts/manticore-speaks-mysql-so-i-made-it-a-laravel-database-driver-instead-of-a-scout-engine-ttlilubi5) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Manticore Speaks MySQL — So I Made It a Laravel Database Driver Instead of a Scout Engine","url":"https://daily.dev/posts/manticore-speaks-mysql-so-i-made-it-a-laravel-database-driver-instead-of-a-scout-engine-ttlilubi5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/manticore-speaks-mysql-so-i-made-it-a-laravel-database-driver-instead-of-a-scout-engine-ttlilubi5"},"datePublished":"2026-07-17T12:50:52.235Z","dateModified":"2026-09-14T06:00:02.703Z","description":"A Laravel database driver for Manticore Search that leverages Manticore's MySQL wire protocol compatibility to expose it as a first-class Eloquent connection....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d6ab0a9a223ee01bc82d647f54feb2d2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d6ab0a9a223ee01bc82d647f54feb2d2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/manticore-speaks-mysql-so-i-made-it-a-laravel-database-driver-instead-of-a-scout-engine-ttlilubi5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"php,laravel,full-text-search,manticore-search","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"Manticore Speaks MySQL — So I Made It a Laravel Database Driver Instead of a Scout Engine"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/manticore-speaks-mysql-so-i-made-it-a-laravel-database-driver-instead-of-a-scout-engine-ttlilubi5#faq","mainEntity":[{"@type":"Question","name":"How can I use Laravel Eloquent directly with Manticore Search instead of Laravel Scout?","acceptedAnswer":{"@type":"Answer","text":"Manticore Search accepts MySQL wire protocol connections on port 9306, so a custom Laravel database driver with a dialect-specific grammar can register it as a first-class Eloquent connection. The laravel-manticore-eloquent package does this, giving models, migrations, pagination, casts, and chunking directly on Manticore instead of the limited search() call Scout exposes. Developers weighing Scout against a native driver for Manticore can compare real tradeoffs surfaced on daily.dev."}},{"@type":"Question","name":"Can I do KNN vector search using Laravel's query builder without a separate vector database?","acceptedAnswer":{"@type":"Answer","text":"Yes, Manticore supports native KNN search, and because the Eloquent driver compiles builder calls straight into Manticore SQL, a knn() method plugs into the same query builder used for regular queries. It can be combined with selectRaw for knn_dist(), pagination, and casts, removing the need for a separate vector database in the stack. Anyone consolidating vector search into an existing stack can track real-world approaches like this on daily.dev."}},{"@type":"Question","name":"What are the limitations of using Manticore Search as if it were a MySQL database in Laravel?","acceptedAnswer":{"@type":"Answer","text":"Manticore lacks transactions and row locks, so lockForUpdate() is a no-op and DB::transaction() semantics don't apply. UPDATE only modifies non-text attribute columns, requiring REPLACE INTO to rewrite text fields. Manticore owns document ids, so migrations skip any declared id column. Cross-index JOINs are restricted, and the driver forces PDO emulated prepares since server-side prepared statement support is limited. Teams evaluating Manticore for production search workloads can weigh these gotchas via coverage on daily.dev."}}]} ```