Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: pl./sql deployment stragegies?
On Wed, 29 Sep 2004, mcstockX_at_Xenquery .com wrote:
>
> "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
>| > >schema (version control schema), test schemas, and finally >| > >production schema(s)? >| > > >| > >Since PL/SQL code dependencies are determined at compile >| > >time, this
>| > >some interesting challenges. >| > > >| > >++ mcs >| > > >| > >| > >| > Toad supports Sourcesafe >| > >| > >| > -- >| > Sybrand Bakker, Senior Oracle DBA >| >|
We have an instance per developer, and at any point, the database code can be checked out and created by typing a command.
This strategy is used to deploy to the more controlled environments, but this time from particular tagged versions of the sourcebase.
> 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?
I also like the suite of schemas per developer. The main point is isolation for accuracy.
-- Galen BoyerReceived on Wed Sep 29 2004 - 17:06:24 CDT