editions based redefinitions to replace individual schema objects concept
Hello,
Just wanted to get some opinion.
Oracle db : 11.2.0.2
Our company has only one schema where all objects reside in the design database and developers add code, modify objects etc within that same schema and invalidate other code and other developers sometimes spend a lot of hours around this.
We personally thought to use editions based redefinitions to resolve this , that way, each developer could modify code in his own edition and other developers are unaware of the change and unaffected.
Would this be ok and if we go this route, how does this affect the current tablespace and what other issues could we expect.
Lets say we re talking 10 developers.
Thanks.