• Comments posted to this topic are about the item Constraints

    [font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
    Connect to me on LinkedIn

  • Thanks, good question.


  • Cool!!!

  • Thanks, a very good question!

  • Very good question

    I shouldn't try to think this early!


  • This was removed by the editor as SPAM

  • Thought this was straightforward but sadly not

    Surprised that the NULL was not caught in the check constraint...

    More coffee required.


    Note to developers:
    So why complicate your code AND MAKE MY JOB HARDER??!:crazy:

    Want to get the best help? Click here (Jeff Moden)
    My blog:
    Visit to find out more about me.

  • Had already had first coffee before attempting to answer this. 😀

    Good question, thanks

  • good and easy question!!!


    [font="Times New Roman"][/font]
    DBA - SQL Server 2008

    remember is live or suffer twice!
    the period you fastest growing is the most difficult period of your life!
  • Thanks for the question. I was pretty sure the check constraint would allow the NULL value.

  • From

    CHECK constraints reject values that evaluate to FALSE. Because null values evaluate to UNKNOWN, their presence in expressions may override a constraint. For example, suppose you place a constraint on an int column MyColumn specifying that MyColumn can contain only the value 10 (MyColumn = 10). If you insert the value NULL into MyColumn, the Database Engine inserts NULL and does not return an error.

  • Good and easy Question !!!


    Vinay Kumar
    Keep Learning - Keep Growing !!!

  • Great question. I got it right, but only because I have encountered this behavior before, and committed it to memory.



  • Thanks for a good question. I got it right, but I thought that perhaps only one such NULL INSERT would be allowed. After reading the BOL entry and trying it out, I see that you can INSERT many such rows.

    Odd behavior, at least to me, as it seems the "correct" interpretation of this should be "only permit the INSERT if the constraint condition evaluates to TRUE."

    Anyone here know if this is an ANSI-compliant implementation? Is this how constraints work in MySQL, Oracle, DB2? Just curious....

    Learned something new and got my point!


  • I guess the answer is wrong

    It should be 1 and 2 only

    beacuse only the constraint is violated,

    the sql statement is terminated.

    it doesn't look for other statements...

    just goes out of loop.

    Just wat i think this, bcoz i encountered this before..



    Sushant Kumar

Viewing 15 posts - 1 through 15 (of 32 total)

You must be logged in to reply to this topic. Login to reply