Message-Id: <46EBC2CB0200003400012820@mailhost.groupwise.msstate.edu>
Date: Sat, 15 Sep 2007 11:32:27 -0500
From: "Doug Gernaat" <dag@its.msstate.edu>
To: "Jared Still" <jkstill@gmail.com>
Cc: <oracle-l@freelists.org>
Subject: Re: publish a pl/sql pkg
References: <46EAAE3B020000340001279A@mailhost.groupwise.msstate.edu>
 <bf46380709150819v7489a2bxdc4f9b1a74ff906c@mail.gmail.com>
In-Reply-To: <bf46380709150819v7489a2bxdc4f9b1a74ff906c@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-to: dag@its.msstate.edu

haha... exactly right!

this started out as a small in-house type app.
now other external units need to do SOME of
the same programming that we have done.
while other units do their own development,
there might be security concerns where we feel
that this SOME should not be done in multiple
environments. so now... there are talks about
standards - and offering up what we have done
to others as that possible standard(which sounds
reasonable to me).

thanks for the info
-doug-


>>> "Jared Still" <jkstill@gmail.com> 9/15/2007 10:19:02 AM >>>
On 9/14/07, Doug Gernaat <dag@its.msstate.edu> wrote:
>
> i got a pl/sql pkg with some functions and procedures in it.
> it's working beautifully for other programs that use it within
> the same database environment.
>
> if i were to make this available to other depts within our
> enterprise, what route might you take? these other depts
> are using diff programming languages and databases for
> their web apps.
>
>
Sharing is a great idea.

Just keep in mind what will happen if people make use of it.

* enhancements will be requested.  You will have to make them.
* bugs may be found.  You will have to fix them
* whatever data it relies on will be changed.  You will have to modify the
code.

You will be maintaining this code for as long as you are with the company.

It's not that I am trying to put a damper on your enthusiasm, you just have
to realize that no good deed goes unpunished.  ;)

Been there, done that.  The most recent example is an app that had a fairly
good database design, and worked fairly well.  The rules changed, I spent
80 hours (or more) adapting it, and I am still responsible for it.  It will
need
changed again soon due to changes in its data sources.

There's nothing wrong with this, other than it tends to interfere with
everything
else that a DBA normally does, which all adds up to extra time spent
working.

I've learned to be more careful what I volunteer for. :)

Just food for thought...
-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--
http://www.freelists.org/webpage/oracle-l