Reviewing Oracle To Postgres Migration

1---2name: reviewing-oracle-to-postgres-migration3description: 'Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting, timestamps, concurrent transactions, etc.). Use when planning a database migration, reviewing migration artifacts, or validating that integration tests cover Oracle/PostgreSQL differences.'4---5 6# Oracle-to-PostgreSQL Database Migration7 8Surfaces migration risks and validates migration work against known Oracle/PostgreSQL behavioral differences documented in the `references/` folder.9 10## When to use11 121. **Planning** — Before starting migration work on a procedure, trigger, query, or refcursor client. Identify which reference insights apply so risks are addressed up front.132. **Validating** — After migration work is done, confirm every applicable insight was addressed and integration tests cover the new PostgreSQL semantics.14 15## Workflow16 17Determine the task type:18 19**Planning a migration?** Follow the risk assessment workflow.20**Validating completed work?** Follow the validation workflow.21 22### Risk assessment workflow (planning)23 24```25Risk Assessment:26- [ ] Step 1: Identify the migration scope27- [ ] Step 2: Screen each insight for applicability28- [ ] Step 3: Document risks and recommended actions29```30 31**Step 1: Identify the migration scope**32 33List the affected database objects (procedures, triggers, queries, views) and the application code that calls them.34 35**Step 2: Screen each insight for applicability**36 37Review the reference index in [references/REFERENCE.md](references/REFERENCE.md). For each entry, determine whether the migration scope contains patterns affected by that insight. Read the full reference file only when the insight is potentially relevant.38 39**Step 3: Document risks and recommended actions**40 41For each applicable insight, note the specific risk and the recommended fix pattern from the reference file. Flag any insight that requires a design decision (e.g., whether to preserve Oracle empty-string-as-NULL semantics or adopt PostgreSQL behavior).42 43### Validation workflow (post-migration)44 45```46Validation:47- [ ] Step 1: Map the migration artifact48- [ ] Step 2: Cross-check applicable insights49- [ ] Step 3: Verify integration test coverage50- [ ] Step 4: Gate the result51```52 53**Step 1: Map the migration artifact**54 55Identify the migrated object and summarize the change set.56 57**Step 2: Cross-check applicable insights**58 59For each reference in [references/REFERENCE.md](references/REFERENCE.md), confirm the behavior or test requirement is acknowledged and addressed in the migration work.60 61**Step 3: Verify integration test coverage**62 63Confirm tests exercise both the happy path and the failure scenarios highlighted in applicable insights (exceptions, sorting, refcursor consumption, concurrent transactions, timestamps, etc.).64 65**Step 4: Gate the result**66 67Return a checklist asserting each applicable insight was addressed, migration scripts run, and integration tests pass.