首页/测试 & QA/creating-oracle-to-postgres-migration-bug-report
C

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

by @githubv
4.3(35)

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

bug-reportingdatabase-migration-testingoracle-to-postgresqlquality-assuranceGitHub
安装方式
npx skills add https://github.com/github/awesome-copilot --skill creating-oracle-to-postgres-migration-bug-report
compare_arrows

Before / After 效果对比

1 组
使用前

迁移过程中发现Bug,报告不规范,难以有效追踪和解决。

使用后

生成清晰规范的Bug报告,加速问题定位与修复,保障迁移质量。

SKILL.md

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. 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 Installs234Repositorygithub/awesome-copilotGitHub Stars25.7KFirst Seen7 days agoSecurity AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled ongemini-cli202codex201opencode194cursor193kimi-cli191github-copilot191

用户评价 (0)

发表评价

效果
易用性
文档
兼容性

暂无评价

统计数据

安装量1.8K
评分4.3 / 5.0
版本
更新日期2026年10月7日
对比案例1 组

用户评分

4.3(35)
5
49%
4
51%
3
0%
2
0%
1
0%

为此 Skill 评分

0.0

兼容平台

🔧Claude Code

时间线

创建2026年3月18日
最后更新2026年10月7日
🎁 Agent 知识卡片
调研问卷