- What is webman/database and how does it relate to Laravel?
- It is the database component for the webman framework that adapts Laravel's illuminate/database layer, giving you the query builder, Eloquent ORM, schema builder, and pagination inside Workerman-based resident-memory services. It is not a Laravel package; it exists to bring Laravel-style database ergonomics and connection pooling to webman apps.
- How do I install webman/database?
- Install it with Composer as webman/database in a webman project and let webman's plugin auto-discovery register it. Configuration lives in webman's config/database.php or plugin config path and mirrors a typical Laravel database config, so you define connections, drivers, and pool settings there. Schema migrations need webman/console or another runner.
- Does webman/database support Laravel 13 and illuminate/database ^13.0?
- Version 2.1.10 widens the constraint to illuminate/database ^10.0 || ^11.0 || ^12.0 || ^13.0, so Composer will permit Laravel 13 components in the same dependency tree. However, a constraint bump alone does not prove the package's test suite runs against Laravel 13. Treat 13.x as resolver-permitted but not validated until upstream CI matrix coverage or your own parity tests confirm it.
- Should I use webman/database in Laravel or Laravel Octane?
- No. In Laravel, Laravel Octane, or PHP-FPM you should use illuminate/database directly; webman/database is built for webman/Workerman, optionally Swoole or Swow coroutine runtimes, and its connection pool and plugin config path do not fit Laravel's bootstrap. Its value is carrying Laravel-shaped APIs and existing Eloquent models into a webman service with minimal rewrite, not replacing Laravel's own DB layer.
- How does connection pooling work and is it safe for long-running webman workers?
- webman/database adds a managed connection pool so PDO connections are reused safely across requests in webman's resident-memory model, avoiding the singleton-per-process connection exhaustion you get with vanilla illuminate/database under many workers. The main risk area is connection affinity for transactions and session state, so test transaction-heavy code carefully. The v2.1.10 release does not change pool behavior.
- Can I reuse my existing Eloquent models and relationships with webman/database?
- Yes, it provides support\Model and support\Db with Laravel-compatible Eloquent APIs, including relationships, model events, and common query builder features, so most repository and model code is portable from Laravel. Container-dependent behavior such as observers or global scopes bound through service providers needs explicit re-binding because webman does not ship Laravel's full container. Plan for that when migrating.
- How do I run migrations and schema changes with webman/database?
- The package includes schema builder and migration support, but you need a console runner such as webman/console to execute migrations in a webman project. This is the main tooling piece that does not come automatically from Laravel familiarity. Once the console plugin is installed, commands follow the familiar Laravel migration workflow.
- Which databases and PDO drivers are supported by webman/database?
- It works with MySQL, PostgreSQL, SQLite, and SQL Server through common PDO drivers, and supports multiple database connections configured in webman's config/database.php. Driver-specific behavior and pool debugging can differ across plain Workerman, Swoole, and Swow runtimes, so confirm your target runtime and driver combination in staging. The package is a database component, not a driver abstraction beyond what illuminate/database already provides.
- What changed in webman/database v2.1.10 and do I need to upgrade?
- Version 2.1.10 only widens the illuminate/database constraint to include ^13.0; there are no API changes, deprecations, behavioral changes, or listed bug fixes. Upgrade if you need Composer to resolve alongside illuminate/* 13.x components in a shared tree or monorepo. Otherwise it is a compatibility-ceiling raise, not a feature release, so plan it as dependency maintenance.
- Is webman/database production-ready and well maintained?
- It is MIT-licensed and is effectively bundled infrastructure for the webman framework, so its real adoption is through webman rather than the standalone repository's star count or dependents. Treat it as single-maintainer infrastructure and verify the actual release tag before pinning, because the v2.1.10 diff is a manifest constraint change only. Run your own parity and pool tests, especially around transactions, before relying on it in production.