XPost: comp.databases.oracle.misc, comp.databases.oracle.server   
      
   "Mark C. Stock"  wrote:   
      
   > yes, in theory, the SQL Server approach is more 'pure', but in practice,   
   > the Oracle approach is more practical (i'm starting to sound like yogi   
   > berra!)   
   >   
   > if i'm creating a UNIQUE constraint, my goal is to disallow values that   
   > are known to be equal to other known values -- so, it's entirely   
   > appropriate to not disallow (sorry for the double-negs) unknown values   
   > (triple-negs?) since there is no known basis for excluding them   
      
   But then why does it exclude them when there are other columns present?   
      
   Xho   
      
   --   
   -------------------- http://NewsReader.Com/ --------------------   
   Usenet Newsgroup Service                        $9.95/Month 30GB   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)