634453e2   
   XPost: microsoft.public.sqlserver.programming   
   From: genew@ocis.net   
      
   On Thu, 14 Jul 2011 07:12:12 -0700 (PDT), --CELKO--   
    wrote:   
      
   >On Jul 12, 3:12 pm, Gene Wirchenko  wrote:   
   >> Dear SQL'ers:   
   >>   
   >>      Is there any way around the SQL glitch that a check condition   
   >> will always succeed when the table is empty?   
   >>   
   >>      I do not want to have the first row be automatically accepted.   
      
   >Glitch? That is a law of logic; anything you say about non-existing   
   >thigns is true. Look up "Existental import" in a text book on the   
      
        It would be a glitch if it turned out to be truth.  A vacuous   
   truth is irrelevant.   
      
   >history of modern logic. And teh first row is not always accepted.   
      
        I have now read that it is in two places.  Given the weirdnesses   
   and dysfunctionalities of SQL, it was not unbelieveable.  I am glad it   
   is wrong.   
      
   > I have some situations with self-references to avoid gaps in the   
   >dates of a history that I start with CHECK() constraints off, insert a   
   >first row, turn teh DRI back on and proceed to insert as usual.   
      
        Please expand "DRI".   
      
   Sincerely,   
      
   Gene Wirchenko   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)