Database and SQL

The Hibernate Criteria API uses addOrder() method to add sorting, not setOrder() or add(). The method takes an Order object like Order.asc("name") or Order.desc("name").

Native SQL queries in Hibernate are executed using createSQLQuery() method which accepts raw SQL strings. Option C uses the correct syntax. Option A uses HQL (createQLQuery), Option B uses incorrect SQL, and Option D incorrectly mixes HQL syntax with SQL.

The flush() method synchronizes the session state with the database, executing all pending SQL statements. commit() commits the transaction, close() closes the session, and list() returns query results. flush() is what actually ensures SQL execution.

Hibernate basic value types include integer, character, yes_no (boolean mapping), string, date, and many others. Since all options A, B, C are valid basic types, the correct answer is 'None of the above' (meaning none is NOT a basic type).

Hibernate uses the 'show_sql' property to print all executed SQL statements to the console. This is a boolean configuration property that enables SQL logging for debugging purposes.

%ROWCOUNT is a cursor attribute that returns the number of rows fetched by the cursor so far. It is a numeric value that increments with each successful fetch operation.

PL/SQL has two types of cursors: implicit cursors (automatically created by Oracle for SQL statements) and explicit cursors (explicitly declared and managed by the programmer).

The correct structure of an explicit cursor is: OPEN cursor, FETCH cursor INTO variables, process the data, then CLOSE cursor. Option B correctly shows this complete lifecycle with FETCH statement included.

The %FOUND cursor attribute returns a BOOLEAN value (TRUE if a row was fetched, FALSE if not). It does not return NUMBER, CHARACTER, or STRING types.

The default parameter mode for procedures is IN. IN parameters pass values into the procedure but cannot be modified within the procedure.

Procedures accept three parameter modes: IN (read-only input), OUT (write-only output), and INOUT (read and write). These modes control how data flows between the procedure and calling environment.

In Oracle database name resolution, when a reference is ambiguous (could refer to a local object or a public synonym), the local schema objects take precedence. Your own HR table in your schema will be accessed instead of the public synonym HR that points to GENERAL.HUMAN_RESOURCES.

SQL views can be created with the WITH CHECK OPTION to make them read-only, preventing inserts or updates through the view. Views can also be created as joins of two or more tables to present combined data. However, standard SQL prohibits ORDER BY in view definitions - ordering belongs in queries accessing the view. Views can use GROUP BY for aggregation.

A main query can indeed contain multiple subqueries in different clauses (WHERE, FROM, SELECT). Subqueries and main queries can access entirely different tables - they're independent queries. When comparing a subquery result to the main query in a WHERE clause, only one column or expression can be compared (this is the scalar subquery pattern). Option B is false because a subquery is nested within one main query, not multiple.

Level 66 is specifically used for the RENAMES clause in COBOL. It allows you to regroup existing data elements by giving a new name to a contiguous set of elementary items. Level 88 is for condition names, and level 77 is for independent elementary items.