An objective person can compartmentalize their feelings, and has to in order to be objective. They cannot let their feelings get in the way of their thought processes. They rely on data and facts, not emotion when considering things. Depending on what the "question" is, they may consider the emotions of themselves and others as "factors" but do not allow them to control their thinking.

If a person is getting all emotional, if they're making fast defensive statements, they're not being objective. They may be "rational" but that is not the same thing as objective.

One of the Merriam Webster definitions of objective is: "expressing or dealing with facts or conditions as perceived without distortion by personal feelings, prejudices, or interpretations"

My Answer: No. I find that objective people, are usually,very difficult to have a sensible discussion with.
Most things in life are subjective and anybody who isn't aware of this, is probably, very young, or very limited in their perception and experience, of life.

Data independence means that "the application is independent of the storage structure and access strategy of data". In other words, The ability to modify the schema definition in one level should not affect the schema definition in the next higher level.

Two types of Data Independence:

Ø Physical Data Independence: Modification in physical level should not affect the logical level.

Ø Logical Data Independence: Modification in logical level should affect the view level.

NOTE: Logical Data Independence is more difficult to achieve

Indexing is a technique for determining how quickly specific data can be found.

Types:

Ø Binary search style indexing

Ø B-Tree indexing

Ø Inverted list indexing

Ø Memory resident table

Ø Table indexing

PL/SQL exception handling is a mechanism for dealing with run-time errors encountered during procedure execution. Use of this mechanism enables execution to continue if the error is not severe enough to cause procedure termination.

The exception handler must be defined within a subprogram specification. Errors cause the program to raise an exception with a transfer of control to the exception-handler block. After the exception handler executes, control returns to the block in which the handler was defined. If there are no more executable statements in the block, control returns to the caller.