Re: packages - one file or separate

From: Jacek Gębal <jgebal_at_gmail.com>
Date: Wed, 13 Sep 2017 21:59:39 +0100
Message-ID: <CACQ9E3tTY1+GeKckt6TFPQ6mMLu8KBJCXpigCtdLvzG-jO5JNg_at_mail.gmail.com>



Separate files for me definitely.
Sonar analysis for code coverage requires separate files per analysed object.
So 1 file = 1 db object (trigger/table/package spec/package body/function/procedure/type spec/type body)

Jacek

On 13 September 2017 at 20:27, William Robertson < william_at_williamrobertson.net> wrote:

> Separate files for me too. You lose the tabbed editor window in PL/SQL
> Developer but I don't really notice it.
>
> William
>
> On 13 Sep 2017, at 16:31, Michael Cunningham <napacunningham_at_gmail.com>
> wrote:
>
> Similar to what Norman said I use separate files and it is primarily due
> to the way the TOAD development environment works. TOAD separates them, so
> that's how I do it. Norman had a good point about being able to modify the
> body without invalidating the package.
>
> Michael
>
>
>
> Sent from my iPhone
> On Wed, Sep 13, 2017 at 8:00 AM, Jeff Chirco <backseatdba_at_gmail.com>
> wrote:
>
>> We put all our database code in files and use a source control. We’ve
>> always stored our package header and body in a single file. We use PL/SQL
>> Developer and it handles that packages in a single file and opens the
>> header and body in nice separate tabs. We getting ready to move out source
>> control to Git and wondering if now is the time to split up our package
>> files into separate files. The benefit I guess is that we are not
>> compiling the header when nothing has changed. Currently when they made an
>> update to the package body the developers will send us the file containing
>> the header and so both get recompiled in production. Which unless I am
>> mistaken forces referencing objects to recompile. Only checking out the
>> body would prevent that but then we have more files to check out when we
>> need the header.
>>
>> So I am curious what is better or more common? I’ve been also looking
>> around at tools that manage the source control like Datical and Red Gate.
>> Although Datical is ridiculously expensive. Anyways these tools seem to
>> prefer packages in separate files.
>>
>> What does everyone here do?
>>
>> Thanks,
>> Jeff
>>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Sep 13 2017 - 22:59:39 CEST

Original text of this message