IMHO there is no big, but fundamental problem: - if your app rely on more then one _significant_ optional field - your ER model sucks - NULL compared to anything gives false, even NULL=NULL
solution: build a db view per optional field, null-'key' rows will vanish, not the denormalized table what you are trying to accomplish is a case clause in SQL, as we know: every case statement could be outfactored better by working on your model ;-) bax View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836342#3836342 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3836342 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
