Extradoctrine Bundle Laravel Package

Product Decisions This Supports

• Legacy System Modernization: Justifies extending existing Symfony2/Doctrine-based systems with custom DQL functions (e.g., LPAD) without rewriting core logic.
• Cost-Effective Customization: Avoids building proprietary Doctrine extensions for niche use cases (e.g., string padding in queries) when the bundle offers a lightweight alternative.
• Roadmap for Deprecation: Supports a phased migration plan for Symfony2 projects by patching gaps until a full rewrite is feasible.
• Data Transformation Use Cases: Enables complex query logic (e.g., concatenating formatted dates) without application-layer post-processing, reducing overhead.
• Build vs. Buy: Favors "buy" for one-off DQL needs over maintaining custom Doctrine listeners or abstract syntax tree (AST) nodes.

When to Consider This Package

• Avoid if:
  • Using Symfony 3+ or 4+: Bundle is incompatible (targets Symfony2) and unmaintained.
  • Requiring active maintenance: No stars, dependents, or updates since 2015; risk of breaking changes in newer Doctrine versions.
  • Needing multiple custom functions: Bundle only provides LPAD; other use cases (e.g., RPAD, TRIM) would require forking or extending.
  • Security-critical projects: Unvetted codebase with no recent activity.
  • Modern alternatives exist: Prefer Doctrine extensions (e.g., gedmo/doctrine-extensions) or query builders for newer Symfony.
• Consider if:
  • Maintaining a Symfony2 monolith with no near-term migration plans.
  • Requiring minimal, one-off DQL functions (e.g., string padding) without dependency bloat.
  • Constrained by budget/time to build custom solutions.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us add simple database functions (like string padding) to our Symfony2 queries without rewriting core logic. It’s a low-risk, zero-cost way to handle niche data formatting needs—like generating standardized date strings—while we plan our long-term migration. Since it’s MIT-licensed and lightweight, it won’t block future upgrades."

For Engineering: "The ExtraDoctrineBundle provides a pre-built LPAD DQL function for Symfony2, saving us from implementing a custom Doctrine AST node. It’s a drop-in solution for cases like formatting month values (e.g., LPAD(month, 2, '0')), but note it’s unmaintained and Symfony2-only. We’d need to vet the code and have a fallback plan if it breaks with Doctrine updates. Alternatives like Gedmo’s extensions are more robust but require Symfony 3+."

For Architects: "This bundle is a temporary band-aid for legacy systems. It’s not a strategic choice—it’s a way to avoid reinventing the wheel for a single function. If we’re stuck on Symfony2, it’s better than nothing, but we should pair it with a migration timeline to move to supported tools (e.g., Doctrine Extensions or native query builders)."