Weave Code
Doctrine Dump Fixtures Bundle Laravel Package
jupeter/doctrine-dump-fixtures-bundle
Symfony bundle for exporting Doctrine database contents as reusable fixture classes. Generate fixtures from existing data via a console command, simplifying test data setup and development seeding.
Symfony DoctrineDumpFixturesBundle
Frequently asked questions about Doctrine Dump Fixtures Bundle
- Can I use jupeter/doctrine-dump-fixtures-bundle in a Laravel app?
- No. It is a Symfony 2 bundle that registers through AppKernel and the Symfony DependencyInjection container, and it has no Illuminate service provider, package auto-discovery, or Artisan command. A Laravel app cannot load it without booting a second framework container, which is not a reasonable trade for a dev-tooling feature. Use an Eloquent-native alternative instead.
- What Laravel versions does this package support?
- None. The package is built for Symfony 2.x and Doctrine ORM, not Laravel, so there is no supported Laravel version, config merge path, or Artisan integration. Its Symfony 2.8 baseline reached end of security support in November 2019. Do not add it to a Laravel composer.json expecting framework integration.
- How do I install jupeter/doctrine-dump-fixtures-bundle?
- In a legacy Symfony 2 application you would require jupeter/doctrine-dump-fixtures-bundle via Composer, register the bundle in AppKernel, and run its Symfony Console command to dump database contents into fixture classes. Installation in a Laravel project is not supported because there is no service provider or auto-discovery. Check PHP and Symfony constraints before attempting any install, because they sit below modern 8.x baselines.
- What does this bundle actually do?
- It reads Doctrine ORM metadata for entities and associations, selects rows from the existing database, and generates Doctrine-compatible fixture files that can be reloaded to seed a database. It preserves relationship ordering so foreign keys resolve when fixtures are loaded. The output is reusable fixture classes, not Laravel seeders.
- Does jupeter/doctrine-dump-fixtures-bundle work with Eloquent?
- No. It depends on Doctrine ORM metadata and Doctrine fixtures, so it only understands Doctrine entities and associations, not Eloquent models. If your Laravel stack uses Eloquent only, this bundle has nothing to introspect. You would need Doctrine via laravel-doctrine even to approximate its workflow, and even then the Symfony bundle wiring remains a blocker.
- Is this package maintained and safe to use in production?
- Treat it as unmaintained and development-only. It has very low adoption, a single maintainer, and no dependents, so there is little chance of a patch if something breaks. Its Symfony 2.8 and older PHP constraints are end-of-life, which will typically fail Composer resolution or trip SCA and compliance gates. The risk is supply-chain and lifecycle, not necessarily code quality.
- What are the Laravel alternatives for generating seeders from an existing database?
- For Eloquent, orangehill/iseed reverse-seeds a live database into Laravel seeder classes, and spatie/laravel-db-snapshots handles environment refresh and database snapshots. Those are maintained, Eloquent-native tools that solve the same developer-tooling job without a Symfony container. Evaluate them before considering any port of this bundle's dump algorithm.
- What Symfony and PHP versions does this bundle require?
- It is a Symfony 2 bundle, with Symfony 2.8 having reached end of security support in November 2019, and its PHP constraints are below the 8.x baseline most estates now run. Those constraints are the hard blocker: Composer will either fail resolution or resolve a stale subtree into your lockfile. Even legacy Laravel 5.x lines tolerating PHP 7.x would face DBAL and ORM version conflicts.
- Can I port the dump logic into a Laravel Artisan command?
- Yes, and that is the realistic option. The functional surface is small: introspect Doctrine metadata, select rows, serialize to fixture or seeder files, and preserve foreign-key ordering. A competent Laravel engineer can reproduce it as a single Artisan command in roughly one to three days, using Eloquent metadata or schema introspection. Record the decision in an ADR so the same evaluation is not repeated later.
- How should I test fixtures generated by this bundle?
- The generated files are Doctrine fixtures, so they load through Doctrine's data-fixtures tooling in a Symfony or Doctrine-enabled environment, not through Laravel's db:seed. In a Laravel project you would instead assert against seeder output or use database snapshots for deterministic test setup. If you need deterministic test fixtures, prefer factories and explicit seeders over dumping a live database, and gate any production-adjacent dump behind a PII-scrubbing policy.
Weaver
How can I help you explore Laravel packages today?