RE: MODERATOR ALERT

On 07/06/2004 at 10:23:35 PM, java400-l-bounces@xxxxxxxxxxxx wrote:
In a procedural language, such programming requires an intimate
knowledge of the database, a detailed understanding of the business
requirements, and some really solid programming skills.  It's a
completely different process than creating yet another "Select and
Display" program.
--- end of excerpt ---

Hi Joe.
  Viewing things from a different perspective, I would view this as a 
negative 
aspect of the programming language/applictaion environment. 

  So, can you explain a bit about how this model reacts to changes in the
database and what schemes are typically used to minimize such 
changes or make them tranparent?

  Additional tables, changes in columns type, sizes usages?
  Fields that are not clean and and databases that are not designed well
One example I've seen is where char fields represent different scalar data 

(even different units) depending on the values of other fields. The units 
were
in yet another field in a psuedo-standard way because of the age and 
growth
characteristics of the database.

  How do you address those things in general?


"The stuff we call "software" is not like anything that human society 
  is used to thinking about. Software is something like a machine, and 
  something like mathematics, and something like language, and 
  something like thought, and art, and information... 
  but software is not in fact any of those other things."
Bruce Sterling - The Hacker Crackdown

Fred A. Kulack - IBM eServer iSeries - Enterprise Application Solutions
ERP, Java DB2 access, Jdbc, JTA, etc...
IBM in Rochester, MN  (Phone: 507.253.5982   T/L 553-5982)
mailto:kulack/us.ibm.com   Personal: mailto:kulack/magnaspeed.net
AIM Home:FKulack  AIM Work:FKulackWrk 
MSN Work: fakulack/hotmail.com (replace email / with @)