Sql Laravel Package

Product Decisions This Supports

• Feature scoping: Use psx/sql as a tactical accelerator for features that need typed PHP representations of an existing database schema—especially read models, DTOs, reporting payloads, admin screens, and integration adapters—without hand-writing boilerplate.
• Legacy modernization roadmap: Evaluate it for incrementally exposing legacy or non-Laravel databases through typed PHP classes while the team decides whether to migrate toward Eloquent, Doctrine, or a custom data-access layer.
• Build vs. buy: Treat it as a low-cost “buy/borrow” option for schema-to-code generation under Apache-2.0. Compare against building a custom generator or adopting Laravel-native conventions such as Eloquent models, migrations, factories, and IDE helpers.
• Architecture decision: Clarify whether the product needs plain type-safe classes or a full ORM. psx/sql is not a substitute for Laravel’s Eloquent relationship lifecycle, migrations, and query ergonomics; it is better framed as a typed schema-contract generator.
• Quality and CI decisions: Pilot generated classes in CI to detect schema drift, enforce static analysis, and reduce runtime type errors. Measure generation stability, regeneration diffs, and developer onboarding cost before expanding usage.
• Risk decision: Because the package has low visible adoption—17 stars, 0 dependents, low opportunity score—avoid making it a foundational dependency for core domain models until a time-boxed pilot proves value.

When to Consider This Package

Consider psx/sql when:

• The database schema is the source of truth and the team needs type-safe PHP classes generated from that schema.
• The work is internal, read-heavy, or integration-oriented: admin tooling, reporting, data export, legacy DB access, API DTOs, or static-analysis coverage.
• The team can vendor/fork the package or wrap generation in its own build step, and is comfortable owning generated-code lifecycle and upgrades.
• A lightweight, Apache-2.0 code generator is preferable to building schema introspection and class generation from scratch.
• The product does not require Laravel-native Eloquent models, relationships, migrations, factories, or active-record behavior for the generated classes.

Look elsewhere when:

• The team expects a Laravel-first ORM experience with Eloquent relationships, query builder integration, lifecycle hooks, and migration tooling.
• The package would become a long-term core dependency and the organization requires strong ecosystem validation, frequent releases, or broad community support.
• The schema changes frequently and the team lacks a reliable regeneration, diff review, and CI validation process.
• The feature needs complex write models, domain behavior, authorization-aware persistence, or multi-database abstraction beyond simple typed mapping.
• The cost of adapting a non-Laravel package exceeds the cost of using Laravel-native tooling or a small custom generator.

How to Pitch It (Stakeholders)

Executive summary: psx/sql is a small Apache-2.0 PHP package that generates type-safe PHP classes from a database schema. It is worth a time-boxed pilot for legacy-schema integrations, read models, and typed DTOs—not a strategic platform bet. Its low adoption signals—17 stars and 0 dependents—mean we should treat it as a tactical accelerator with an ownership plan, not a default dependency for core product domains.

For engineering: The package can reduce hand-written mapping code and improve static analysis when the database schema is authoritative. The trade-off is integration and ownership: it is not a Laravel-native ORM, generated classes may not fit Eloquent conventions, and we must control regeneration, diffs, and upgrades. Run a short spike against one non-critical schema, measure time saved and maintenance overhead, and define exit criteria before broader adoption.

Decision requested: Approve a limited pilot in an internal or read-only feature, with a go/no-go gate based on developer velocity, schema-drift safety, and total ownership cost. Do not standardize it across core domain models until the pilot proves a clear advantage over Laravel-native or custom-generated alternatives.