RE: publish a pl/sql pkg
- From: "Robert Freeman" <robertgfreeman@xxxxxxxxx>
- To: <jkstill@xxxxxxxxx>, <dag@xxxxxxxxxxxxxxx>
- Date: Sun, 16 Sep 2007 19:32:18 -0600
I seem to have found a solution to that problem. It's called become a
manager. Then no one expects anything of a technical value out of you! :-)
RF
Robert G. Freeman
Oracle Consultant/DBA/Author
Principal Engineer/Team Manager
The Church of Jesus Christ of Latter-Day Saints
Father of Five, Husband of One,
Author of various geeky computer titles
from Osborne/McGraw Hill (Oracle Press)
Oracle Database 11g New Features Now Available for Pre-sales on Amazon.com!
BLOG: http://robertgfreeman.blogspot.com/
Sig V1.2
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Jared Still
Sent: Saturday, September 15, 2007 9:19 AM
To: dag@xxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: publish a pl/sql pkg
On 9/14/07, Doug Gernaat <dag@xxxxxxxxxxxxxxx> 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
Other related posts:
