DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=PXhwYb8BVdmXJdhz4cvcMCPCwEN5fl4fAwJBJS2MawrCVXZKQSO7Z72jd92WF4EwiZNKgMu9XXxUcajIDE3Ucrtv8FE3yCQlceSEp+5+mqkxxVw2GTI7y78XLm5/Yuohpj2cl6/G1M5+E8je4JdzA1fAdN1/Cp60QmSWXMVhJ6A=
Message-ID: <bf46380709150819v7489a2bxdc4f9b1a74ff906c@mail.gmail.com>
Date: Sat, 15 Sep 2007 08:19:02 -0700
From: "Jared Still" <jkstill@gmail.com>
To: dag@its.msstate.edu
Subject: Re: publish a pl/sql pkg
Cc: oracle-l@freelists.org
In-Reply-To: <46EAAE3B020000340001279A@mailhost.groupwise.msstate.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_5385_11473437.1189869542759"
References: <46EAAE3B020000340001279A@mailhost.groupwise.msstate.edu>
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-to: jkstill@gmail.com
------=_Part_5385_11473437.1189869542759
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------=_Part_5385_11473437.1189869542759
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 9/14/07, <b class="gmail_sendername">Doug Gernaat</b> &lt;<a href="mailto:dag@its.msstate.edu">dag@its.msstate.edu</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
i got a pl/sql pkg with some functions and procedures in it.<br>it&#39;s working beautifully for other programs that use it within<br>the same database environment.<br><br>if i were to make this available to other depts within our
<br>enterprise, what route might you take? these other depts<br>are using diff programming languages and databases for<br>their web apps.<br><br></blockquote></div><br>Sharing is a great idea.<br><br>Just keep in mind what will happen if people make use of it.
<br><br>* enhancements will be requested.&nbsp; You will have to make them.<br>* bugs may be found.&nbsp; You will have to fix them<br>* whatever data it relies on will be changed.&nbsp; You will have to modify the code.<br><br>You will be maintaining this code for as long as you are with the company.
<br><br>It&#39;s not that I am trying to put a damper on your enthusiasm, you just have<br>to realize that no good deed goes unpunished.&nbsp; ;)<br><br>Been there, done that.&nbsp; The most recent example is an app that had a fairly
<br>good database design, and worked fairly well.&nbsp; The rules changed, I spent<br>80 hours (or more) adapting it, and I am still responsible for it.&nbsp; It will need<br>changed again soon due to changes in its data sources.<br>
<br>There&#39;s nothing wrong with this, other than it tends to interfere with everything<br>else that a DBA normally does, which all adds up to extra time spent working.<br><br>I&#39;ve learned to be more careful what I volunteer for. :)
<br><br>Just food for thought...<br>-- <br>Jared Still<br>Certifiable Oracle DBA and Part Time Perl Evangelist<br>

------=_Part_5385_11473437.1189869542759--
--
http://www.freelists.org/webpage/oracle-l