Weave Code
Laravel Tarantool Laravel Package
chocofamilyme/laravel-tarantool
Laravel integration for Tarantool that lets you use the in-memory database with Eloquent-style models, a query builder, migrations, and queue support, making it easy to add fast Tarantool storage to your existing Laravel application.
A Tarantool based Eloquent ORM and Query builder for Laravel
Frequently asked questions about Laravel Tarantool
- What is chocofamilyme/laravel-tarantool used for?
- It is a Laravel integration for Tarantool that provides an Eloquent-style ORM, query builder, migrations, and queue support. It lets existing Laravel applications use Tarantool as fast in-memory storage without abandoning familiar model and query patterns. It is intended for teams already using or evaluating Tarantool, not for standard MySQL or PostgreSQL-only Laravel stacks.
- How do I install chocofamilyme/laravel-tarantool?
- Install it with Composer using composer require chocofamilyme/laravel-tarantool, then follow the package README for service provider and configuration publishing steps. You will need a reachable Tarantool instance and connection settings in your Laravel configuration. Confirm the package and Laravel version constraints in Composer before installing it in an existing application.
- Which Laravel versions does laravel-tarantool support?
- The package is built for Laravel, but the exact supported Laravel versions depend on the release and its Composer constraints. Check the package composer.json and README for the current compatibility matrix before upgrading. Teams should verify compatibility in staging, especially when using newer Laravel query grammar behavior.
- Does laravel-tarantool support Eloquent models and relationships?
- The package provides a Tarantool-based Eloquent ORM and query builder, so you can use model-style access and fluent query building similar to Laravel's database layer. The overview highlights ORM, query builder, migrations, and queue support. Complex relationship behavior should be verified against the package documentation and your Tarantool schema.
- Does laravel-tarantool support migrations and Laravel queues?
- Yes, migration support and queue support are both part of the package's stated feature set. Migrations let you manage Tarantool spaces and indexes alongside application code, while queues can use Tarantool storage. Review the README for exact migration syntax, queue driver configuration, failure handling, and persistence expectations before production use.
- What changed in laravel-tarantool 1.1.2 for UNION queries?
- Version 1.1.2 adjusts the Tarantool query grammar by overriding wrapUnion and removing parentheses around union subqueries. This aligns generated SQL with Tarantool's expected UNION syntax for supported cases. The change matters most to applications using union queries, nested unions, ordering, limiting, or pagination.
- Are nested UNION queries with orderBy, limit, and offset tested in laravel-tarantool?
- The available assessment flags nested unions combined with ordering, limiting, and pagination as an area that must be verified. It does not confirm comprehensive test coverage for every combination. Teams should add regression tests for their actual union query shapes before upgrading, especially in reporting or raw SQL paths.
- Is laravel-tarantool safe in a multi-database Laravel application?
- The grammar override is intended for Tarantool connections, but mixed-database environments are identified as the highest-risk failure mode. Removing parentheses from union subqueries can be correct for Tarantool while conflicting with assumptions in shared grammar code or other database connections. Test each connection separately and avoid applying Tarantool-specific query behavior to MySQL or PostgreSQL queries.
- What are alternatives to chocofamilyme/laravel-tarantool?
- If you need a conventional relational database, Laravel's built-in MySQL, PostgreSQL, or SQLite drivers are the standard alternatives. If you specifically need Tarantool, compare this package with direct Tarantool client libraries or a custom query layer. This package is most compelling when you want Eloquent-style models, query builder, migrations, and queues inside Laravel rather than raw Tarantool access.
- How do I upgrade and maintain laravel-tarantool in production?
- Treat 1.1.2 as a patch upgrade: update via Composer, run union-query regression tests, and validate representative application flows in staging. Ongoing maintenance includes tracking Laravel query grammar changes because the package overrides wrapUnion for Tarantool. Document the override, keep targeted tests, and monitor query exceptions after rollout.
Weaver
How can I help you explore Laravel packages today?