Weave Code
Ai Doctrine Message Store Laravel Package
symfony/ai-doctrine-message-store
symfony/ai-doctrine-message-store integrates Doctrine DBAL with Symfony AI Chat to provide database-backed message storage. It lets AI chat applications persist conversation messages through Doctrine, with resources and contributions handled in the main Symfony AI repository.
Doctrine Message Store provides Doctrine DBAL-backed persistence for Symfony AI Chat, letting you store conversations and messages in any database supported by Doctrine. It implements the Symfony AI message store abstraction, so chat history survives across requests and can be queried, paginated, or pruned as needed.
- DBAL-backed storage for conversations and chat messages
- Drop-in implementation of the Symfony AI message store interface
- Works with MySQL, PostgreSQL, SQLite and other Doctrine platforms
- Schema managed through Doctrine migrations or your existing tooling
- Efficient querying and pagination of stored message history
Frequently asked questions about Ai Doctrine Message Store
- What is symfony/ai-doctrine-message-store used for in a Laravel app?
- It provides a Doctrine DBAL-backed message store for Symfony AI Chat, storing AI conversation messages in relational tables. In Laravel, it is useful only if you already use Symfony AI Chat or can adapt its message store interface; it is not a native Laravel AI package. It fits audit, compliance, or SQL-queryable chat history use cases.
- How do I install symfony/ai-doctrine-message-store with Composer?
- Run composer require symfony/ai-doctrine-message-store and ensure doctrine/dbal is installed. You also need a compatible Symfony AI Chat version and a database connection configured through Doctrine DBAL or Laravel's doctrine/dbal integration. Check the main Symfony AI repository for exact version constraints because issues and PRs are handled there.
- Does this package work with Laravel out of the box?
- No, it is a Symfony AI Chat bridge, not a Laravel package, and Laravel does not natively provide Symfony AI Chat or its message store wiring. You would need a custom adapter or facade to use the store inside Laravel. Doctrine DBAL itself works in Laravel, but the AI chat integration layer is the main gap.
- Which Laravel versions can use symfony/ai-doctrine-message-store?
- There is no official Laravel version matrix for this package; compatibility depends on doctrine/dbal, PHP, and any custom adapter you write. Modern Laravel releases that support doctrine/dbal v3.x are the practical target. Validate against your app's PHP and Laravel constraints before adding it to production.
- How should I configure the Doctrine DBAL message store in Laravel?
- Configure a Doctrine DBAL connection using Laravel's database settings, then pass that connection into the package's message store as required by Symfony AI Chat. Avoid mixing package-managed schema with existing Laravel migrations without a plan. Prefer explicit migrations or Doctrine tools so table ownership is clear.
- Do I need to create database migrations for the message store tables?
- The package relies on relational tables for stored chat messages, but you should confirm the expected schema from the Symfony AI Doctrine message store implementation. In Laravel, create migrations with the Schema builder or use Doctrine Migrations if that fits your workflow. Do not assume auto-migration; schema conflicts with existing Laravel tables are a real risk.
- Is symfony/ai-doctrine-message-store suitable for high-volume AI chat logging?
- Doctrine DBAL relational storage is a good fit for structured queries, auditing, and compliance, but it may add latency compared with Redis or in-memory stores for very high throughput. For high-volume interactions, consider a hybrid approach: relational storage for durable/queryable records and Redis for hot-path message buffering. Benchmark against your expected message rate before committing.
- Can I use this package without Symfony AI Chat?
- It is designed as a Doctrine DBAL message store bridge for Symfony AI Chat, so using it without that consumer requires implementing or adapting the expected message store contract. That means extra integration work and maintenance risk. If you only need Laravel-native AI chat storage, a Laravel-specific package or a custom database store may be simpler.
- What are alternatives to symfony/ai-doctrine-message-store for Laravel AI chat storage?
- Alternatives include Laravel-native AI packages, custom Eloquent or query-builder message stores, Redis-backed stores for high throughput, and other Symfony AI message store implementations. Choose based on whether you need SQL joins, auditability, or low-latency buffering. A hybrid relational plus Redis design often covers both compliance and performance.
- How is symfony/ai-doctrine-message-store maintained and where do I report issues?
- It is part of the Symfony AI ecosystem, with issues and pull requests handled in the main symfony/ai GitHub repository rather than a separate issue tracker. Maintenance follows Symfony AI's release cadence, so check version compatibility with Symfony AI Chat and Doctrine DBAL. For Laravel teams, factor in the cost of tracking a Symfony-centric dependency.
Weaver
How can I help you explore Laravel packages today?