- Can I use pfilsx/postgresql-doctrine-bundle in a Laravel app?
- Not as intended. The package is a Symfony bundle that depends on Symfony's kernel, bundle registration and configuration tree, while Laravel uses Eloquent and its own migration runner. Doctrine DBAL ships with Laravel only as an optional dependency for schema introspection, and Doctrine Migrations is not part of the standard runtime. You could cherry-pick individual DBAL platform or schema classes into an internal namespace, but that shifts maintenance to your team and requires verifying class-level coupling to Symfony interfaces.
- What PostgreSQL features does this Doctrine bundle add?
- It provides extended Doctrine DBAL types and platform/schema integration so PostgreSQL-native columns such as arrays, JSONB and other advanced types can be mapped in Doctrine entities and diffed by Doctrine Migrations. Because the repository has no test suite or detailed documentation, the exact scope for enums, partial and expression indexes, and schema diffing is unverified. Treat the feature list as a starting point to validate against your specific PostgreSQL schema.
- How do I install pfilsx/postgresql-doctrine-bundle?
- Installation is via Composer with composer require pfilsx/postgresql-doctrine-bundle, followed by registering the bundle in a Symfony kernel and configuring it through the bundle's configuration tree. There is no Laravel service provider, no package discovery support and no published Laravel installation path. In a Laravel app, installation is only meaningful if you isolate the DBAL and migration classes manually.
- Which PHP, Doctrine DBAL and Symfony versions are supported?
- The available README excerpt does not publish explicit version constraints, and the last release was in February 2023, so current compatibility with Doctrine DBAL 3.x/4.x, Doctrine Migrations, Symfony 6/7 and PHP 8.2+ must be checked in composer.json before any review. Expect friction with modern Laravel releases that pin newer DBAL versions. Verify the PHP constraint, DBAL major version and Symfony framework version first.
- Does it work with Doctrine Migrations in Laravel?
- Doctrine Migrations is not part of the standard Laravel runtime, so the bundle's migration integration does not plug into Laravel's own migrator. Adding it would create a second migration system with separate tracking tables, ordering and rollback semantics. Laravel's native schema builder plus raw DB::statement migrations is the supported path for the same PostgreSQL features.
- Is pfilsx/postgresql-doctrine-bundle still maintained?
- The repository has four stars, zero dependents and a last release in February 2023, which suggests abandoned or near-abandoned maintenance. There is no evident security or compatibility backport path, and no external evidence that the extension points remain compatible with current DBAL or PHP releases. Adopting it means taking ownership of upgrades and fixes yourself.
- Can I use the DBAL platform classes without the Symfony bundle?
- That is the only realistic integration route for a Laravel codebase, but it requires checking whether the platform and migration classes reference Symfony container interfaces or bundle lifecycle hooks. Run a time-boxed spike in a scratch bare-PHP or Symfony harness against your target PostgreSQL version and record the behaviour. If the classes prove standalone, fork only the needed files into an internal namespace with MIT attribution rather than depending on upstream.
- What are the alternatives for PostgreSQL arrays and JSONB in Laravel?
- Laravel's schema builder covers many common types, and raw DB::statement migrations, custom schema macros or generated SQL baselines handle arrays, JSONB, enums and expression indexes with no extra dependency. Those approaches keep a single migration system and a single ownership model. Inventory which schema features Laravel cannot express or diff correctly before considering anything else.
- Is there a test suite for schema diff and migration generation?
- No test suite is referenced in the available repository information, so schema diff and migration generation correctness are not demonstrated. Without tests, behaviour for arrays, JSONB, enums, partial indexes and expression indexes is unverified. If you spike the package, write your own assertions around introspection and diff output before trusting it.
- What are the production risks of adopting this package?
- Primary risks are abandoned maintenance, version skew against Doctrine DBAL 3.x/4.x and PHP 8.2+, implicit coupling to Symfony's container and bundle lifecycle, and an unverified feature scope. In production, adoption shifts maintenance ownership to your team. If a specific PostgreSQL feature is genuinely blocking, vendor a minimal fork of the needed classes under MIT attribution and pin it rather than adding a runtime dependency.