Oracle到PostgreSQL存储过程迁移工具：自动翻译PL/SQL为PL/pgSQL

migrating-oracle-to-postgres-stored-procedures by github/awesome-copilot

490 周安装量

26,900 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/github/awesome-copilot --skill migrating-oracle-to-postgres-stored-procedures

开发自动化数据库

🇨🇳中文介绍

从 Oracle 迁移存储过程到 PostgreSQL

将 Oracle PL/SQL 存储过程和函数翻译为 PostgreSQL PL/pgSQL 等价形式。

工作流程

进度:
- [ ] 步骤 1: 读取 Oracle 源过程
- [ ] 步骤 2: 翻译为 PostgreSQL PL/pgSQL
- [ ] 步骤 3: 将迁移后的过程写入 Postgres 输出目录

步骤 1: 读取 Oracle 源过程

从 .github/oracle-to-postgres-migration/DDL/Oracle/Procedures and Functions/ 读取 Oracle 存储过程。请参考 .github/oracle-to-postgres-migration/DDL/Oracle/Tables and Views/ 下的 Oracle 表/视图定义以进行类型解析。

步骤 2: 翻译为 PostgreSQL PL/pgSQL

应用以下翻译规则：

将所有 Oracle 特有的语法翻译为 PostgreSQL 的等价形式。
保留原始功能和控制流逻辑。
保留类型锚定的输入参数（例如 PARAM_NAME IN table_name.column_name%TYPE）。
对于传递给其他过程的输出参数，使用显式类型（NUMERIC、VARCHAR、）——不要对这些参数进行类型锚定。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

Migrating Stored Procedures from Oracle to PostgreSQL

Translate Oracle PL/SQL stored procedures and functions to PostgreSQL PL/pgSQL equivalents.

Workflow

Progress:
- [ ] Step 1: Read the Oracle source procedure
- [ ] Step 2: Translate to PostgreSQL PL/pgSQL
- [ ] Step 3: Write the migrated procedure to Postgres output directory

Step 1: Read the Oracle source procedure

Read the Oracle stored procedure from .github/oracle-to-postgres-migration/DDL/Oracle/Procedures and Functions/. Consult the Oracle table/view definitions at .github/oracle-to-postgres-migration/DDL/Oracle/Tables and Views/ for type resolution.

Step 2: Translate to PostgreSQL PL/pgSQL

Apply these translation rules:

Translate all Oracle-specific syntax to PostgreSQL equivalents.
Preserve original functionality and control flow logic.
Keep type-anchored input parameters (e.g., PARAM_NAME IN table_name.column_name%TYPE).
Use explicit types (NUMERIC, VARCHAR, INTEGER) for output parameters passed to other procedures — do not type-anchor these.
Do not alter method signatures.
Do not prefix object names with schema names unless already present in the Oracle source.
Leave exception handling and rollback logic unchanged.
Do not generate COMMENT or GRANT statements.
Use COLLATE "C" when ordering by text fields for Oracle-compatible sorting.
Leverage the orafce extension when it improves clarity or fidelity.

Consult the PostgreSQL table/view definitions at .github/oracle-to-postgres-migration/DDL/Postgres/Tables and Views/ for target schema details.

Step 3: Write the migrated procedure to Postgres output directory

Place each migrated procedure in its own file under .github/oracle-to-postgres-migration/DDL/Postgres/Procedures and Functions/{PACKAGE_NAME_IF_APPLICABLE}/. One procedure per file.

Weekly Installs

450

Repository

github/awesome-copilot

GitHub Stars

26.7K

First Seen

13 days ago

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

gemini-cli398

codex397

opencode387

cursor384

github-copilot381

kimi-cli380