From: Banana@Republic.com   
      
   David Portas wrote:   
   > Erland,   
   >   
   > How would that be possible in an ACID system though? Suppose I update 1   
   > million rows in a single statement and then the 1 million +1 row causes a   
   > constraint violation. Is my database corrupt?   
   >   
      
   I'm no Erland, but the point isn't so much about constraint violation   
   but rather being able to rollback the changes. If one wanted to update 1   
   million rows, then there has to be enough space to "cache" those   
   affected rows so if something goes wrong, be it constraint violation or   
   something else, it can be rollbacked. But if we allowed update and   
   didn't have big enough logs to write the changes those same changes   
   would then get overwritten and we lose the whole ACID-ity.   
      
   IMHO, it's unfortunate that such thing has made it more painful than   
   actually warranted though I can understand Microsoft's reasoning for not   
   wanting to provide "disable it" button as I do agree with Erland that   
   there's too many people out there who don't stop and think before they   
   push the giant, red button. ;)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)