Examine the description of the EMP_DETAILS table given below:
Which two statements are true regarding SQL statements that can be executed on the
EMP_DETAIL table? (Choose two.)
A.
An EMP_IMAGE column can be included in the GROUP BY clause
B.
You cannot add a new column to the table with LONG as the data type
C.
An EMP_IMAGE column cannot be included in the ORDER BY clause
D.
You can alter the table to include the NOT NULL constraint on the EMP_IMAGE column
Explanation:
LONG Character data in the database character set, up to 2GB. All the functionality of LONG (and
more) is provided by CLOB; LONGs should not be used in a modern database, and if your
database has any columns of this type they should be converted to CLOB. There can only be one
LONG column in a table.
Guidelines
A LONG column is not copied when a table is created using a subquery.
A LONG column cannot be included in a GROUP BY or an ORDER BY clause.
Only one LONG column can be used per table.
No constraints can be defined on a LONG column.
You might want to use a CLOB column rather than a LONG column.
only one long column can by exist for table
Option D is also correct, we can alter the table to add the NOT NULL constraint on a column having LONG datatype.
D is correct: You can alter the table to include the NOT NULL constraint on the EMP_IMAGE column
ref:http://docs.oracle.com/cd/B19306_01/server.102/b14200/sql_elements001.htm#i54330
**LONG columns cannot appear in WHERE clauses or in integrity constraints (except that they can appear in NULL and NOT NULL constraints).