creating-oracle-to-postgres-migration-bug-report

Document the expected Oracle behavior versus the observed PostgreSQL behavior, then add ordered reproduction steps with seed data, the root cause tied to a specific behavioral difference, the solution with file paths, and validation steps. Assign a severity from Low to Critical and a status of resolved, unresolved, or in progress.

Each report includes status, affected component, related tests, severity, problem statement, reproduction scenario, root cause, solution with explicit file paths, validation steps, and notes. The template also requires listing modified files with a short purpose for each change.

Common causes include empty string versus NULL semantics, type coercion strictness, collation differences, sequence values, time zone handling, padding, and constraint enforcement. Reports should name the specific difference as the root cause rather than describing symptoms only.

Reports are saved to .github/oracle-to-postgres-migration/Reports/{ProjectName}/ with filenames in the format BUG_REPORT_<DescriptiveSlug>.md. The project name uses hyphens for spaces, and the slug is a short PascalCase identifier describing the defect.

Client code changes should be avoided unless required for correct behavior, since Oracle is treated as the source of truth. When such changes are proposed, the report must document and justify them explicitly alongside the data access layer modifications.