anonymous
  • anonymous
A seperate CONSTRAINT line is not required when defining a tables primary key? True or false ?? (SQL SERVER)
Computer Science
  • Stacey Warren - Expert brainly.com
Hey! We 've verified this expert answer for you, click below to unlock the details :)
SOLVED
At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
schrodinger
  • schrodinger
I got my questions answered at brainly.com in under 10 minutes. Go to brainly.com now for free help!
mattfeury
  • mattfeury
This seems true to me. In my mind, something like this is totally valid: CREATE TABLE user (Email VARCHAR(20) NOT NULL, Name VARCHAR(20) NOT NULL, Password VARCHAR(20) NOT NULL, Primary Key (Email)); 'Constraint' would be optional.
mattfeury
  • mattfeury
Further clarification: the 'Constraint' keyword is optional only if you want to refer to that constraint value by name later. If not, then sql will generate a name for your constraint. This is useful when there are many constraints and you want to modify them individually by name. had I wanted to name the constraint, I could have written that line as: ... Constraint userKey Primary Key (Email));

Looking for something else?

Not the answer you are looking for? Search for more explanations.