- Can I use dsdeboer/propel1 in a Laravel 9+ project?
- No, this package is designed for PHP5 and Propel 1.x, which are incompatible with Laravel 9+ (requires PHP 8.0+). Laravel’s Eloquent or Doctrine ORM are the only supported options for modern Laravel versions.
- What’s the primary use case for this package?
- The only viable scenario is maintaining a legacy PHP5 application using Propel 1.x while optionally integrating Symfony components. It’s not meant for new Laravel projects or modern PHP stacks.
- How do I install dsdeboer/propel1 in a Laravel project?
- You can’t install it directly in Laravel due to PHP version conflicts. Instead, use Composer in a standalone PHP5 environment (`composer require dsdeboer/propel1`) and manually integrate it via custom service providers or adapters.
- Does this package support Laravel’s service container or Eloquent features?
- No, it lacks native Laravel integration. You’d need to manually wire Propel models into Laravel’s container and replicate features like relationships, events, or query scopes with custom code.
- Are there security risks using Propel 1.x in production?
- Yes, Propel 1.x has unpatched vulnerabilities (e.g., SQL injection risks) and relies on deprecated PHP5 libraries. Avoid it for new projects or production environments unless absolutely necessary for legacy systems.
- Can I migrate from Propel 1.x to Eloquent using this package?
- No, this package doesn’t include migration tools. You’d need to manually convert Propel’s XML/YAML schemas to Laravel migrations and build a custom mapper layer to translate Propel models to Eloquent.
- What databases does Propel 1.x support in Laravel?
- Propel 1.x supports MySQL, PostgreSQL, SQLite, and MSSQL (via ODBC), but Laravel’s Eloquent uses modern PDO drivers. Mixing them risks driver conflicts or inconsistent behavior.
- Is there active maintenance or Laravel compatibility planned?
- No, Propel 1.x is abandoned (last release in 2010). This package is a static integration layer with no updates. Laravel compatibility is impossible without a full rewrite.
- What alternatives exist for legacy Propel 1.x in Laravel?
- For Laravel, use Eloquent (native) or Doctrine DBAL (for raw queries). For PHP5-only apps, consider forking Propel 1.x or migrating to a supported ORM like Propel 2.x (if PHP7+ is an option).
- How do I handle Propel 1.x schema migrations in Laravel?
- Propel uses XML/YAML schemas, while Laravel uses PHP migrations. You’d need a custom script to export Propel schemas to Laravel migrations or use a hybrid approach with Propel’s schema tools alongside Laravel’s.