On Thu, 23 Nov 2006 14:06:49 +0100, Robert Klemme
<shortcutter@googlemail.com> wrote:
snip
Do you mean data *and* logic were in the DB (i.e. stored procedures)?
Or do you mean to say only data is in the DB?
Our legacy system only stored data in the DB.
All procedures and processes were in he code. They were very
"modularized" though, and we could use them in input routines and
reports without any trouble.
The two biggest pluses I see to the relational model for DB, and
please comment on my ideas here for Java since I am new to Java, are
the data is easy to maintain and it is easy to train end users to
understand relational data and to do heir own reports. By maintain I
don't mean the day to day input but rather the data schema over time.
We have had several times when we needed to add serious new
functionality to the system, and by adding a few fields and a few new
reports, we were able to do it without any serious reprogramming of
the scheme or the code.
Can we do this in Java?