Re: [MVC-Programmers] RE: Re: [MVC-Programmers] Design for Requirements

2003-08-14 Thread Vic Cekvenich
:-)

Yes DBA's can have it good. Once there is data... one has to do a very 
expensive data conversion process. (Imagine some records don't make it, 
or some FK-PK references get lost) So almost no one ever changes 
production DB model.

But formbeans must match forms (jsp view) so when a user changes the 
forms (reqs. spec.) ... we follow. Of course then we have O/R impedance 
over time, fun!.

(I have in the past used "temporary" tables )

.V

Peyathevar, Santhi {PBG} wrote:

I always wondered: 

Why does the Object Model have to keep changing with requirements
and not the Database Design !
Santhi :)

--
Vic Cekvenich,
Struts Instructor,
1-800-917-JAVA
Advanced Struts Training, mentoring and 
project recovery in North East.
Struts conversion and  fixed bid development.

___
MVC-Programmers mailing list
[EMAIL PROTECTED]
http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers


RE: Re: [MVC-Programmers] Design for Requirements

2003-08-14 Thread Peyathevar, Santhi {PBG}
I always wondered: 

Why does the Object Model have to keep changing with requirements
and not the Database Design !

Santhi :)

___
MVC-Programmers mailing list
[EMAIL PROTECTED]
http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers