Doctrine Commons Laravel Package

Product Decisions This Supports

• Build vs. buy for DQL plumbing. Custom Doctrine DQL functions (FIELD(), FIND_IN_SET(), DATE_FORMAT(), IFNULL(), GROUP_CONCAT, MATCH … AGAINST) are small but genuinely fiddly to write and test — parser registration, platform-specific SQL generation, parameter type handling. This package is a candidate shortcut that lets you avoid a 1–2 sprint internal library effort.
• ORM strategy for reporting/read models. If you're weighing Doctrine ORM against Eloquent for a reporting module, legacy-system bridge, or an analytics read model, helper packages like this one lower the "Doctrine is more work than Eloquent" argument. That materially affects the roadmap conversation.
• Legacy/porting scope. When porting SQL-heavy legacy queries, DQL function coverage is a real blocker. Knowing what's available off the shelf (versus what you must build) sharpens the estimate for migration epics.
• Reference implementation sizing. Even if you never install it, the source answers "how much code is a DQL function, really?" — useful input for a build-vs-fork decision and for scoping an internal App\Doctrine\DQL namespace.
• Dependency risk register. 0 stars, 0 dependents, 0 transitive consumers means zero external bug-finding and zero community vetting. That drives a vendor/copy-in decision rather than an install-and-pin decision, which is itself a product/architecture call worth recording.

When to Consider This Package

Consider it when:

• You are genuinely running Doctrine ORM — not plain Eloquent. In a standard Laravel app using Eloquent, this package has no applicable surface area and the evaluation ends here.
• You need one or two specific DQL functions that you've confirmed exist in this package and are absent from Doctrine's own function set.
• Your target is MySQL/MariaDB only and you are comfortable with vendor-specific SQL.
• You can pin the version, vendor the code, and own the fork. Apache-2.0 makes that legally clean.
• You've checked beberlei/doctrineextensions first and it doesn't cover your function.

Look elsewhere when:

• You want a maintained, battle-tested dependency — beberlei/doctrineextensions is the de facto standard with broad adoption; prefer it unless it genuinely lacks what you need.
• You're on Eloquent, or on Doctrine DBAL only (no ORM).
• You need multi-platform SQL generation (Postgres + MySQL + SQLite), pagination, or DBAL middleware — this package is not that. Use Pagerfanta/KnpPaginator for pagination.
• You require an SLA, security responsiveness, or a vendor contact. There is none implied here.
• Pre-adoption verification checklist: confirm the repo has tests, confirm the DQL functions parse under your Doctrine ORM version (DQL parser APIs shift between 2.x and 3.x), check last-commit date, and check for open issues. With 0 dependents, you are the first production user — assume you will find the first bug.

How to Pitch It (Stakeholders)

To executives: This is a small, Apache-2.0-licensed helper library for Doctrine-based PHP applications. It is not a strategic dependency and carries no cost, no vendor lock-in, and no commercial exposure — the license permits us to copy what we need and own it. Recommend treating it as reference material, not a dependency: worth ~1 day of engineering review to see whether it saves us building DQL helpers ourselves, not worth a procurement or roadmap line item.

To engineering: Use it as a catalog, not a package. Cherry-pick the specific DQL function(s) you need into App\Doctrine\DQL, retain the Apache-2.0 attribution, and write tests against our actual database version. Do not add it as a runtime dependency: with zero stars and zero dependents there is no external bug-finding, no maintenance signal, and no one to file issues with — we'd be the sole QA. Pulling in the whole package also imports helpers we didn't ask for.

Recommendation: Extract, don't depend. Re-evaluate only if the package gains maintainers and real adoption, or if we standardize on Doctrine ORM and need a larger function surface — in which case go to beberlei/doctrineextensions first.