On Thu, April 16, 2009 08:03, student4life wrote: > > For a team of more than 1 pl/sql developers, could someone inform me > of what the typical development environment setup is out there? The > developers are not allowed to install Oracle server/plsql compiler on > their own machines due to some regulation, so there is only one Oracle > 10G DB server running and therefore, even with the help with Control > Versioning system like Subversion, the developers still need to inform > each other every time any of them needs to compile/test run any of > their plsql packages to avoid potential code conflict. TIA > > > > Just as a for instance here is an environment that I have used in the past.
There are public synonyms to every object that is of interest in the application. Each developer has their own schema that they use. Within that schema there is a choice to either using the public synonym have their own copy of the object. This applies equally to tables or packages or views or any other object that you like. This is fairly lightweight and gets away from someone inadvertantly breaking a build but I fail to see why subversion isnt helping you out with the concurrency issue that you seem to have. Only one person should be working on a particular object at a time anyway. One misconception though is that there is some standalone thing called the PL/SQL compiler. While i am sure that there is such a beast it is not something that you install on your machine like a C++ compiler. Just my nickel's worth Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Oracle PL/SQL" group. To post to this group, send email to Oracle-PLSQL@googlegroups.com To unsubscribe from this group, send email to oracle-plsql-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Oracle-PLSQL?hl=en -~----------~----~----~----~------~----~------~--~---
