Git for application code (PHP) along with PL/SQL code? -


i'm having doubt time ago, , have end leaving sql scripts outside version control (i try encapsulate code in database as can).

but find interesting have version control of both app code , database scripts; having snapshots of database situation (just ddl , stored procedures) in each commit pretty useful.

would have app code , sql scripts in different branches (and having cherry-pick, merge, whatever, many times)?

do think it's idea?

usually, having database-related files e.g. construct database schema or provide migration routines inside application repository fine. after all, application needs database, , repository should provide necessary set up. having scripts there construct database, , import base data required fine.

it include scripts provide test data in order run tests (often referred fixtures).

the thing avoid having production data inside repository. else required application run: include in repository.


Comments

Popular posts from this blog

mysql - FireDac error 314 - but DLLs are in program directory -

git - How to list all releases of public repository with GitHub API V3 -

c++ - Getting C2512 "no default constructor" for `ClassA` error on the first parentheses of constructor for `ClassB`? -