10 developers working on Oracle DB packages using Git.
Currently We compile to shared appdev schema.
Dev A + Dev B both edit pkg1.pkg → whoever compiles last overwrites the other.
Batch testing via Atomic Applications Manager - single fixed DB login to appdev@servicename_oracle.
Cannot add parameters/connections to select before submitting the module.
Developers need immediate batch testing of their development activity.
Has anyone implemented this pattern with Atomic Applications Manager + Oracle developers own schema with public synonymns from application schema?
Any solution for this?
So that dev-a can test his/her changes wihtout overriding dev-b's changes
-------------------------------------------