Re: PL/SQL Package Standards

With my (arguably) small (and "left") brain, it's easier for me to keep track of what's going on
by grouping things into small (3 to 5 screens long) "modules".

If you are "well connected" in your organization / have lot's of communication
and code-sharing, then when white-boarding your project, one can identify major (but small) "modules" which many can use.

The books talk about this, but it knowing what should be shareable comes from experience.

If you are producing pl/sql packages/procedures/scripts etc that no one else (including yourself)
would ever want to use/share, please let us all know so we can avoid you.

<cakilner_at_my-deja.com> wrote in message news:810st5$kvk$1_at_nnrp1.deja.com...
> Does anyone know any standards around developing Packages? It is
> recommended to keep the Packages fairly small? Should everything go into
> packages where possible?
>
> One of the problems I have encountered it we are having a lot of
> problems with space in the shared memory pool. I guess an easy fix
> would be to just bump up the size....but this really isn't an option at
> this point. I do know what a lot of the developers on the system are
> coding using packages and I know one of this is close to 2Meg in
> size...should I recommend we reduce the size of these packages and
> perhaps move some code that it used less frequently into
> procedures/functions that are called from within the package?
>
> Can anyone share any experience in this area?
>
> Thanks,
> Carol Kilner
> ckilner_at_protectair.com
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Thu Nov 18 1999 - 17:28:38 CST