Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Oracle database, large plsql code managment

Tags:

oracle

plsql

I am working on project, where business logic is implemented in oracle database, using plsql. Code base is becoming big and it's management is becoming nightmare.

For example when code base is in Java, C#, ... you have version control system for project, where history is stored, and you are managing project with branches, tags etc. I do not understand how this can be done with pl/sql code which is stored directly in database server.

I want to know for situations like this, what are best practice of managing plsql codebase ?

like image 718
Yoh0xFF Avatar asked Dec 02 '22 23:12

Yoh0xFF


1 Answers

There's no reason to only store PL/SQL in the database just because some client tools default to working that way.

I strongly recommend you choose your favourite source control system and store PL/SQL sources in it. Use an all.sql to create all PL/SQL packages and other create-or-replace objects.

See versioning stored procedures/PLSQL? for an alternative approach but this requires a bit more effort to setup.

like image 181
Colin 't Hart Avatar answered Apr 02 '23 02:04

Colin 't Hart