Platform
Stored procedure conversion that compiles before deploy
Datalobe converts procedures, functions, packages, triggers and views, and proves each one compiles on the target before anything is deployed.
540 of 540
code objects compiled on PostgreSQL 16.4 before deploy
540 code objects
540 of 540 compiled before deploy- 212 procedures
- 96 functions
- 24 packages
- 88 triggers
- 120 views
540 of 540 converted and deployed. Anything that could not be proven went to a named engineer.
What it covers
Which code objects does Datalobe convert?
AI converts the stored code, and the migration assessment lists every object in scope with its issue codes.
Procedures
Converted to PL/pgSQL on PostgreSQL. DBMS_JOB schedules move to pg_cron.Functions
NVL becomes COALESCE and DECODE becomes CASE, as in SALES.FN_ORDER_TOTAL.Packages
Package state and package variables need a new shape on PostgreSQL, as with FIN.PKG_GL_POSTING.Triggers
Deployed last, after the routines and views they depend on.Views
CONNECT BY becomes WITH RECURSIVE, as in INV.V_STOCK_POSITION.Caller changes
Flagged in the Migration Plan. Example run: 9 result-set procedures became set-returning functions, “caller change needed: CALL to SELECT”.
How it works
How does code-object conversion work?
AI drafts the code, checks and named engineers prove it, and only code that compiles is deployed.
1. AI converts stored code
AI converts procedures, functions, triggers and complex views.
- NVL to COALESCE
- DECODE to CASE
2. Every AI conversion is checked
Its result columns must match the source, and it is test-called on the target. Nothing AI-written is deployed silently.
- Result columns match
- Test-called on the target
3. People for the rest
Anything not proven goes to a named engineer to accept, edit or rewrite. Datalobe records who did what and when.
- Accept
- Edit
- Rewrite
4. Compile, then deploy in order
Each object must compile on the target first; on PostgreSQL, inside a transaction that is rolled back. Then routines, views and triggers deploy in order.
- 540 of 540 compiled
Showcase
What converts, and how?
Five objects from the example run, each compiled on the target before deploy.
| Object | Source pattern | Result on PostgreSQL |
|---|---|---|
| SALES.FN_ORDER_TOTAL (function) | NVL, DECODE | COALESCE, CASE |
| INV.V_STOCK_POSITION (view) | CONNECT BY | WITH RECURSIVE |
| FIN.PKG_GL_POSTING (package, 14 procedures) | Package state | Schema fin_pkg_gl_posting, functions, session settings table |
| HR.PRC_PAYROLL_CLOSE (procedure) | DBMS_JOB | Schedule moved to pg_cron |
| SALES.TRG_ORDER_AUDIT (trigger) | Autonomous transaction | Rewritten, caller change flagged |
Related
Related features
- Data migration validationFunctions run on source and target, results compared.
- How Datalobe uses AIHow AI drafts stored code and how drafts are checked.
- Migration assessmentEvery code object in scope, with its issue codes.
Questions
Frequently asked questions
Does all code convert automatically?
No. AI converts the stored code, every AI conversion is checked, and engineers review or rewrite anything that cannot be proven. In the example run, Daniel Ortiz rewrote HR.PRC_PAYROLL_CLOSE by hand.
How do you know converted code works?
Every object must compile on the target before deploy. After the migration, deterministic read-only functions run on the same inputs on source and target, and the results are compared. See code-object validation.
What happens to Oracle packages?
PostgreSQL has no packages, so a package needs a new shape. In the example run, Marcus Reed edited the AI draft of FIN.PKG_GL_POSTING into schema fin_pkg_gl_posting with functions and a session settings table.
Which AI model does Datalobe use?
Your organisation sets the AI model provider. See how Datalobe uses AI.
Sources (17)
- PostgreSQL 16 Documentation: 918 Conditional Expressions, checked
- Oracle Database 19c SQL Language Reference: NVL, checked
- Oracle Database 19c SQL Language Reference: DECODE, checked
- Oracle Database 19c Data Warehousing Guide: SQL for Analysis and Reporting, checked
- Oracle Database 19c SQL Language Reference: Hierarchical Queries, checked
- PostgreSQL 16 Documentation: 78 WITH Queries (Common Table Expressions), checked
- PostgreSQL 16 Documentation: 4313 Porting from Oracle PL/SQL, checked
- Oracle Database 19c PL/SQL Packages and Types Reference: DBMS_JOB, checked
- Oracle Database 19c Administrator's Guide: Support for DBMS_JOB, checked
- Oracle Database 19c PL/SQL Language Reference: 13.4 AUTONOMOUS_TRANSACTION Pragma, checked
- PostgreSQL 16 Documentation: CALL, checked
- PostgreSQL 16 Documentation: 38.5 Query Language (SQL) Functions, checked
- PostgreSQL 16 Documentation: 431 Overview (PL/pgSQL), checked
- PostgreSQL 16 Documentation: BEGIN, checked
- PostgreSQL 16 Documentation: ROLLBACK, checked
- PostgreSQL wiki: Transactional DDL in PostgreSQL: A Competitive Analysis, checked
- pg_cron (citusdata/pg_cron on GitHub): Run periodic jobs in PostgreSQL, checked
Demo
See your own procedures converted
Book a demo and bring an object you are worried about.