I�m doing the architecture on a (j2ee) project and I have a disagreement
with one of the analists who is also the DataBase Designer of the project.
First of all, imho, the database design has to follow the UML model for
the application and not the application follow the database model since
my classes might have some other requirements that are not described in
the use cases and because the database design might contain fields I
wont need in my application.
Second, the dba is convinced that the database must contain foreign keys
and constraints. IMHO, the one of the ideas behind J2EE is using each
tier for which it has been designed, as such i think a j2ee application
should not contain any contraints and foreign keys since they might be
very database dependent and would take away part of the portability of
the application and most of all, the application i�m designing has a
shitload of db transactions (20000 inserts 20000 deletes and some 20000
selects every 300 seconds) so constraints and foreign keys really would
screw up my db performance.
Any opinions ?
Sven
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
