Which of the following CANNOT be used to restrict specific values from being inserted into a column in a particular table?
a. check constraint
b. referential constraint
c. view
d. index
answer is view?
thanks any help would be great!

no, I believe index, because with view you can specify where predicate and restrict data that apply to this predicate

I would also answer index since the only thing it can do is restrict with unique which allows only one value to be inserted, but the value CAN be inserted.

A view only restricts if the view is being used to do the insert. If the inserts are directly to the underlying table, the data will be inserted.

Andy

I don't know the correct answer either. The question says "Which of the following CANNOT be used to restrict specific values from being inserted into a column in a particular table?" Thus, one could argue that "views" is the answer if table is meant to be understood as "base table". But for "index" speaks the wording "specific value" because - as Andy said - an index allows any value at least once.

Hi,
what a confusing question... This question requires some explanations.
Grofaty

They tell you to provide the "best" answer". As stated above, a unique index can only prevent dups, not prevent a specific value from being inserted. It appears that all of the other answers can prevent a specific value (if set up correctly) from being inserted.

I would say "views". In views you cannot restrict inserting values. You can restrict on what columns you can have but not the values.

That's not correct; you can restring inserting values via views. If you insert data through a view, you can implement values-based constraints:
The point is that you have to insert into the view (a view is just a table) and not the underlying base table. What is not clear with the initial question is the meaning of the phrase "inserted into a ... particular table". Does it mean that the INSERT operation goes directly against the base table and the base table only? Or can it be directed against the view instead?

Thinking about it, I'd say that "index" is probably the expected answer. The question doesn't say unique index (and a non-unique index doesn't restrict anything), and one could control access to the base table with privileges and only allow data modifications through the view. In fact, you could rename the base table and create the view with the original base table name. Thus, applications wouldn't even know the difference (assuming that static SQL statements are rebound).

They typed "specific value". For example: how you should best deny to user insert value 'xxx' into column ?
And this can not be achieved by any index.