Weave Code
Doctrine Fixes Bundle Laravel Package
ruvents/doctrine-fixes-bundle
Symfony bundle that patches common Doctrine ORM and DBAL quirks so entities and queries behave predictably. It collects targeted fixes for known bugs and edge cases, cutting workarounds from your app code. Install with Composer and register the bundle.
At a glance
Frequently asked questions about Doctrine Fixes Bundle
- What does ruvents/doctrine-fixes-bundle do?
- It is a Symfony bundle that collects targeted fixes for common Doctrine ORM and DBAL quirks. The goal is to make entities and queries behave predictably and remove workarounds from your application code. It is not a general-purpose ORM replacement; it patches known bugs and edge cases.
- How do I install ruvents/doctrine-fixes-bundle?
- Install it with Composer using composer require ruvents/doctrine-fixes-bundle. Then register the bundle in your Symfony application, following the README for version-specific details. Because it is a Symfony bundle, it is not installed as a Laravel service provider.
- How do I register the bundle in Symfony?
- For Symfony Flex applications, add the bundle to config/bundles.php. For older Symfony versions, register it in AppKernel::registerBundles(). The overview says to install with Composer and register the bundle, so check the README for the exact class name and any environment-specific instructions.
- Does ruvents/doctrine-fixes-bundle work with Laravel?
- Not natively. It is a Symfony bundle, and Laravel does not register Symfony bundles in its service container. Laravel's default Eloquent ORM does not use Doctrine ORM/DBAL, so the fixes are not directly applicable. If you use Doctrine in Laravel through a third-party integration, you would need to port the relevant fixes or find a Laravel-specific package.
- Which Doctrine ORM and DBAL versions does it support?
- The package targets Doctrine ORM and DBAL, but the exact supported versions are defined in its Composer constraints. Check composer.json or Packagist for the current requirements before installing. Since it is a Symfony bundle, also confirm compatibility with your Symfony version rather than assuming support for every ORM/DBAL release.
- Is it safe to use in production?
- It is intended to be a normal Composer dependency, but you should review the fixes and run your test suite before deploying. Because it changes Doctrine behavior at the bundle level, test entity mappings, queries, and migrations in a staging environment. Pin a known-good version and monitor for updates.
- Do I need to configure anything after installing?
- The overview describes it as a bundle you register, but it does not mention required configuration. Start by following the README and checking whether any fixes are opt-in or controlled by bundle config. If no configuration is documented, the defaults should apply once the bundle is registered.
- How can I verify the Doctrine fixes are working?
- Run your existing Doctrine-related unit and integration tests after registering the bundle. Add regression tests for the specific quirks you were working around, such as entity hydration or DBAL type handling. Compare query results and generated SQL before and after enabling the bundle, especially if you remove app-level workarounds.
- What are alternatives to this bundle?
- Alternatives include keeping your own Doctrine event subscribers or patches, upgrading Doctrine to a version that fixes the issue, or using other Doctrine extension bundles. The right choice depends on whether the quirks you hit are covered by this bundle and whether you want a Symfony-specific dependency. For Laravel-only projects, a Laravel Doctrine integration or Eloquent workaround is more appropriate.
- Is the package actively maintained?
- Check Packagist, the GitHub repository, and the README for the latest release and maintenance status. Since the overview does not list a support policy, review recent commits and issue activity before adopting it. You can report bugs or contribute fixes via the repository's issue tracker and pull requests.
Weaver
How can I help you explore Laravel packages today?