Re: pl/sql application build & release
From: Jeremy <jeremy0505_at_gmail.com>
Date: Thu, 3 May 2012 09:54:11 +0100
Message-ID: <MPG.2a0c58106ec785f39899a5_at_News.Individual.NET>
In article <4fa246a1$0$10734$5b6aafb4_at_news.zen.co.uk>, dontwantany_at_nowhere.invalid says...
>
> Jeremy wrote:
>
> > In article <7f94df17-94ac-42f7-8f66-ccc8f5fc5c02
> > _at_e42g2000yqa.googlegroups.com>, johnthehurley_at_gmail.com says...
> > >
> > > Hope this helps somewhat and I am sure some other people will report
> > > back what they are doing in their environments.
> > >
> >
> > Perhaps they're being shy.
>
> Or perhaps they just use manual scripts too? Fwiw, that's what we've
> always done, & it's mostly worked ok. However for reasons I won't bore
> you with, we've now split the app into two schemas; one for the tables,
> sequences & triggers, t'other for everything else.
>
> So subject to hitting any problems with the process, future releases
> will be done by exporting the 'code' schema from the 'release' DB &
> importing it on the destinations[1]. Table changes & triggers will
> still be done with the manual scripts. So still no tools involved, but
> an alternative approach to throw into the mix.
>
> [1] Currently 12 dotted around the UK & Ireland.
Date: Thu, 3 May 2012 09:54:11 +0100
Message-ID: <MPG.2a0c58106ec785f39899a5_at_News.Individual.NET>
In article <4fa246a1$0$10734$5b6aafb4_at_news.zen.co.uk>, dontwantany_at_nowhere.invalid says...
>
> Jeremy wrote:
>
> > In article <7f94df17-94ac-42f7-8f66-ccc8f5fc5c02
> > _at_e42g2000yqa.googlegroups.com>, johnthehurley_at_gmail.com says...
> > >
> > > Hope this helps somewhat and I am sure some other people will report
> > > back what they are doing in their environments.
> > >
> >
> > Perhaps they're being shy.
>
> Or perhaps they just use manual scripts too? Fwiw, that's what we've
> always done, & it's mostly worked ok. However for reasons I won't bore
> you with, we've now split the app into two schemas; one for the tables,
> sequences & triggers, t'other for everything else.
>
> So subject to hitting any problems with the process, future releases
> will be done by exporting the 'code' schema from the 'release' DB &
> importing it on the destinations[1]. Table changes & triggers will
> still be done with the manual scripts. So still no tools involved, but
> an alternative approach to throw into the mix.
>
> [1] Currently 12 dotted around the UK & Ireland.
ta
-- jeremyReceived on Thu May 03 2012 - 03:54:11 CDT