Doctrine Prefix Bundle Laravel Package

Product Decisions This Supports

• Database Schema Standardization: Enables consistent table/column naming conventions (e.g., bor_users, sac_email) across microservices or multi-tenant SaaS applications, reducing schema conflicts.
• Multi-Tenant Architecture: Simplifies tenant isolation by auto-applying prefixes (e.g., tenant1_orders, tenant2_orders) without manual schema modifications.
• Legacy System Integration: Accelerates migration paths for existing apps by wrapping legacy tables/columns with prefixes (e.g., legacy_user_profiles → app_user_profiles).
• Build vs. Buy: Avoids reinventing custom Doctrine event listeners or naming strategies for prefixing, reducing dev effort.
• Roadmap Alignment: Supports future-proofing for:
  • Shared database environments (e.g., Heroku, PaaS).
  • Schema-as-code initiatives where naming consistency is critical.

When to Consider This Package

• Adopt if:

  • Your app uses Doctrine ORM and requires consistent table/column prefixes (e.g., multi-tenancy, shared DBs).
  • You’re migrating legacy schemas and need automated prefixing.
  • Your team lacks bandwidth to build a custom naming strategy.
  • You prioritize simplicity over fine-grained control (e.g., dynamic prefixes per entity).

• Look elsewhere if:

  • You need dynamic prefixes (e.g., per-request/tenant) – this is static.
  • Your database isn’t Doctrine ORM-compatible (e.g., Eloquent, raw SQL).
  • You require column-level exclusions (e.g., skip prefixing for id columns).
  • The last release (2020) is a dealbreaker for long-term support (consider forking or alternatives like gedmo/doctrine-extensions).
  • You’re using Doctrine DBAL directly without ORM.

How to Pitch It (Stakeholders)

For Executives:

"This package lets us enforce consistent database naming conventions—critical for scaling our multi-tenant SaaS or integrating legacy systems—without custom dev work. For example, it auto-prefixes tables like bor_users and columns like sac_email, reducing schema conflicts and migration risks. It’s a lightweight, battle-tested solution (used in 8+ repos) that cuts dev time by weeks. The tradeoff? Minimal maintenance (last updated 2020), but we can mitigate that by forking or pairing it with a monitoring alert for updates."

For Engineers:

*"Need to prefix Doctrine tables/columns without writing custom listeners? This bundle drops in via Composer and configures in doctrine_prefix.yaml:

doctrine_prefix:
  table_prefix: app_
  column_prefix: user_

• Pros: Zero PHP code changes, works with any Doctrine ORM app, supports nested strategies (e.g., UnderscoreNamingStrategy).
• Cons: Static prefixes (no runtime flexibility), outdated but functional. Action: Benchmark against alternatives like gedmo/doctrine-extensions if dynamic prefixes are needed. For now, this is a 10-minute win for schema consistency."*