If you really care about it you can add some dummy/reserved columns of common types. Don't use them now, but when you need a new attribute just use one of those reserved columns!! I've seen this trick in an RPG app ;-) But who cares about this issue? Just bring down the server for maintenance and update the database.
Ara. > -----Original Message----- > From: A mailing list for Enterprise JavaBeans development [mailto:EJB- > [EMAIL PROTECTED]] On Behalf Of Mindaugas Kairys > Sent: Tuesday, April 16, 2002 1:29 PM > To: [EMAIL PROTECTED] > Subject: 3rd normal form & EJB > > Hello, > I have such philosophical, but real problem. My Oracle admin asks me, why > are you using such plane database design, what will you do, when it will > come the need for new object attributes: alter tables, change program > code, > stop server....? > > I'd wanted to hear opinions, suggestions, the ways you solve that problem > from you and ask what tools, tips, patterns one should use to archieve > database design of 3rd normal form normalization level using EJB? I know > that CMP entity EJB will be solution to achieve that, but it takes too > much > time. Mhm... > > Mindaugas Kairys > > ======================================================================== == > = > 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". _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com =========================================================================== 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".
