On Sun, Oct 17, 2004 at 01:54:44PM +0200, Thomas Eyde wrote:
> 1st: We, the developers, need full and exclusive control of the
> database. The database should be "private" to our application.
In this particular case, the software package that is
"out of the box" that we customize with triggers/hooks is
both the application that defines the schema and data and
hooks as well as the application that the users use to do
the querying/reporting workflow. The underlying database
can also be manipulated "directly" thru Oracle - but that
is not the interface the users see.
Plus, if we do that we run the risk of breaking the
application because it does certain implementation things
and expects that it is the ONLY thing doing that to the
database and is doing it in a certain way. We can figure
out what that is. And if we try to take advantage of that
we run the risk of being incompatible with the next version
of the software that comes from the vendor because they
reserve the right to be able to change those things
and explicitly warning against relying on such details
from one release to the next.
We can't disallow reporting access to the operational
database because it would be all or nothing. If they can't
use it for reports, then they also cannot use it for the
workflow+data-entry.
--
Brad Appleton <[EMAIL PROTECTED]> www.bradapp.net
Software CM Patterns (www.scmpatterns.com)
Effective Teamwork, Practical Integration
"And miles to go before I sleep." -- Robert Frost
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
