---
id: sm3-creating-oracle-to-postgres-migration-bug-report
name: "creating-oracle-to-postgres-migration-bug-report"
url: https://skills.yangsir.net/skill/sm3-creating-oracle-to-postgres-migration-bug-report
author: github
domain: testing
tags: ["bug-reporting", "database-migration-testing", "oracle-to-postgresql", "quality-assurance"]
install_count: 1800
rating: 4.30 (35 reviews)
github: https://github.com/github/awesome-copilot
---

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

> 为Oracle到PostgreSQL数据库迁移过程中发现的缺陷创建详细的Bug报告，以便追踪和修复。

**Stats**: 1,800 installs · 4.3/5 (35 reviews)

## Before / After 对比

### Oracle到PostgreSQL迁移Bug报告

## Readme

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

# Creating Bug Reports for Oracle-to-PostgreSQL Migration

## When to Use

- Documenting a defect caused by behavioral differences between Oracle and PostgreSQL

- Writing or reviewing a bug report for an Oracle-to-PostgreSQL migration project

## Bug Report Format

Use the template in [references/BUG-REPORT-TEMPLATE.md](https://github.com/github/awesome-copilot/blob/HEAD/skills/creating-oracle-to-postgres-migration-bug-report/references/BUG-REPORT-TEMPLATE.md). Each report must include:

- **Status**: ✅ RESOLVED, ⛔ UNRESOLVED, or ⏳ IN PROGRESS

- **Component**: Affected endpoint, repository, or stored procedure

- **Test**: Related automated test names

- **Severity**: Low / Medium / High / Critical — based on impact scope

- **Problem**: Expected Oracle behavior vs. observed PostgreSQL behavior

- **Scenario**: Ordered reproduction steps with seed data, operation, expected result, and actual result

- **Root Cause**: The specific Oracle/PostgreSQL behavioral difference causing the defect

- **Solution**: Changes made or required, with explicit file paths

- **Validation**: Steps to confirm the fix on both databases

## Oracle-to-PostgreSQL Guidance

- **Oracle is the source of truth** — frame expected behavior from the Oracle baseline

- Call out data layer nuances explicitly: empty string vs. NULL, type coercion strictness, collation, sequence values, time zones, padding, constraints

- Client code changes should be avoided unless required for correct behavior; when proposed, document and justify them clearly

## Writing Style

- Plain language, short sentences, clear next actions

- Present or past tense consistently

- Bullets and numbered lists for steps and validations

- Minimal SQL excerpts and logs as evidence; omit sensitive data and keep snippets reproducible

- Stick to existing runtime/language versions; avoid speculative fixes

## Filename Convention

Save bug reports as `BUG_REPORT_<DescriptiveSlug>.md` where `<DescriptiveSlug>` is a short PascalCase identifier (e.g., `EmptyStringNullHandling`, `RefCursorUnwrapFailure`).
Weekly Installs234Repository[github/awesome-copilot](https://github.com/github/awesome-copilot)GitHub Stars25.7KFirst Seen7 days agoSecurity Audits[Gen Agent Trust HubPass](/github/awesome-copilot/creating-oracle-to-postgres-migration-bug-report/security/agent-trust-hub)[SocketPass](/github/awesome-copilot/creating-oracle-to-postgres-migration-bug-report/security/socket)[SnykPass](/github/awesome-copilot/creating-oracle-to-postgres-migration-bug-report/security/snyk)Installed ongemini-cli202codex201opencode194cursor193kimi-cli191github-copilot191

---
*Source: https://skills.yangsir.net/skill/sm3-creating-oracle-to-postgres-migration-bug-report*
*Markdown mirror: https://skills.yangsir.net/api/skill/sm3-creating-oracle-to-postgres-migration-bug-report/markdown*