Re: pl./sql deployment stragegies?

"Terry Dykstra" <tddykstra_at_forestoil.ca> wrote in message news:OKC6d.3197$Du2.608_at_edtnps89...
| PLSQL Developer also supports Source Control.
|
| --
| Terry Dykstra
| Canadian Forest Oil Ltd.
|
|
| "Sybrand Bakker" <gooiditweg_at_sybrandb.verwijderdit.demon.nl> wrote in
| message news:7lsll05ad0mj47to6k8m3egicok1dvd54c_at_4ax.com...
| > On Wed, 29 Sep 2004 09:25:02 -0400, "Mark C. Stock" <mcstockX_at_Xenquery
| > .com> wrote:
| >
| > >On a multi-developer project, what's your standard/typical way of
| handling
| > >the deployment of PL/SQL packages from developer schemas to a
centralized
| > >schema (version control schema), test schemas, and finally production
| > >schema(s)?
| > >
| > >Since PL/SQL code dependencies are determined at compile time, this
poses
| > >some interesting challenges.
| > >
| > >++ mcs
| > >
| >
| >
| > Toad supports Sourcesafe
| >
| >
| > --
| > Sybrand Bakker, Senior Oracle DBA
|
|

my key interest is deploying from/to and synchronizing master, developer, test, and production schemas

i'm looking for feedback on how many developer schemas (one per developer or shared?), how do you keep schemas in sync (objects and tables), how do you support unit testing and integration testing

ie, developer is working on a revision for package022 which depends on 5 other packages, and 12 tables, and is called via package037 -- typically, are people duplicating the entire application schema for each developer, sharing one development schema, or using some other means?

thanks

++ mcs Received on Wed Sep 29 2004 - 14:07:12 CDT