Db Oracle Laravel Package

Product Decisions This Supports

• Oracle backend strategy: This release is for yiisoft/db-oracle (Yii DB’s Oracle driver), not a Laravel-native package. It supports decisions about whether Oracle remains a supported database backend for Yii-based products and whether to maintain, defer, or retire Oracle-specific support.
• Upgrade vs. feature adoption: 2.0.0 is a major release with breaking API changes, a new PHP floor (8.1), and substantial schema/column/DDL refactoring. PM should treat this as an infrastructure upgrade decision, not a routine patch.
• Build vs. buy for Oracle plumbing: The release expands built-in Oracle schema introspection, column definition building/parsing, type casting, JSON/enum/collation/boolean support, and query-builder behavior. This strengthens the case for using the package instead of maintaining in-house Oracle DDL/DML abstractions.
• Data model and product capability decisions: New support for JSON, enumeration columns, collation, boolean type, binary handling, case-sensitive LIKE, and dropTable options can influence roadmap choices for Oracle-backed features, migrations, and schema management.
• Performance and maintenance investment: Column factory/builder classes and type-specific column classes target schema/type handling performance. PM should weigh upgrade effort against reduced custom code and better compatibility with current yiisoft/db internals.
• Risk management: Breaking changes such as renamed methods, removed TableSchema, changed batchInsert() to insertBatch(), and unsigned-column exceptions create regression risk. The decision should include a compatibility spike and regression-test budget before committing to the upgrade.

When to Consider This Package

• Consider it when the product uses Yii DB / yiisoft/db and needs an Oracle driver for schema introspection, DDL, DML, migrations, or query building.
• Consider 2.0.0 specifically when the team is on PHP 8.1–8.5, can absorb a major-version upgrade, and needs newer Oracle type support such as JSON, enum, collation, boolean, or improved column-definition handling.
• Consider it if the alternative is building and maintaining Oracle-specific column parsing, DDL generation, batch insert, upsert, or schema introspection in-house.
• Look elsewhere if the product is Laravel-first. This is not a Laravel package; a Laravel team should evaluate Laravel’s native database layer, Doctrine DBAL, or direct PDO/OCI8 options unless it already depends on Yii DB.
• Look elsewhere if Oracle is not strategic, if only simple connectivity is needed, or if the team cannot fund regression testing for a major upgrade.
• Be cautious if the product requires vendor SLA/support, cannot tolerate breaking changes, or depends on removed/renamed APIs such as TableSchema, insertWithReturningPks(), or the old batchInsert() signature.

How to Pitch It (Stakeholders)

• Executives: “This is a major maintenance release for our Oracle support layer in Yii DB. It modernizes PHP compatibility, improves Oracle schema/type handling, and reduces custom plumbing, but it is not a user-facing feature and requires planned engineering effort. Approve it only if Oracle remains a supported backend or if dependency updates force the upgrade.”
• Engineering: “2.0.0 is a breaking major release. Plan a compatibility spike first: inventory usages of renamed/removed APIs, update batchInsert() to insertBatch(), replace insertWithReturningPks(), remove reliance on TableSchema, handle unsigned-column exceptions, and run schema/query regression tests against Oracle. Then adopt the new column builders and type support where they reduce custom code.”
• Product framing: “Do not position this as a roadmap feature. Position it as platform hygiene: keep Oracle-backed products maintainable, current on PHP, and aligned with yiisoft/db, while controlling upgrade risk through a scoped migration plan.”