Hibernate ORM Framework

The Hibernate configuration XML uses as its root element. This element contains which in turn contains property definitions and mapping resources. Alternative names like or are not valid Hibernate configuration elements.

Hibernate mapping files can define mappings for multiple classes/tables in a single .hbm.xml file. The root element can contain multiple elements, each mapping a different database table. This provides flexibility in organizing mappings - you can have one file per table or group related tables.

In Hibernate 3 and earlier, the standard way to obtain a SessionFactory from a Configuration object is by calling config.buildSessionFactory(). The other methods do not exist on the configuration object.

The

In Hibernate, integer, character, and yes_no are all valid built-in basic value types. Since all of the listed options are valid basic types, 'None of the above' is the correct choice.

When storing instances of persistent classes in a Java Set, you must override both equals() and hashCode() to ensure correct behavior, as sets rely on these methods to prevent duplicate elements and locate objects.

The flush() method forces Hibernate to synchronize the in-memory state of the session with the underlying database by executing the necessary SQL statements (INSERT, UPDATE, DELETE) immediately, without committing the transaction.

The 'show_sql' property in Hibernate configuration enables logging of all executed SQL statements to the console. This is essential for debugging and understanding what SQL queries Hibernate generates. Other properties like echo_sql, print_sql, and display_sql are not standard Hibernate configuration properties.

Hibernate component classes must implement java.io.Serializable to support caching and detach operations. They should override equals() and hashCode() to work correctly in collections and as map keys. All three requirements ensure proper behavior in Hibernate's persistence framework.

In Hibernate's Criteria API, the addOrder() method is used to apply sorting to the query results, passing an Order object such as Order.asc("name"). The methods setOrder and add are incorrect for this purpose.

To switch the underlying database system, you must update the JDBC driver class, the connection URL, and the Hibernate SQL dialect to match the target database system. Therefore, all of these properties must be changed.

To map and connect to multiple databases in a single Hibernate application, you must configure and instantiate a separate <session-factory> for each database, as a single session factory is tied to one database configuration.

Hibernate supports both Native SQL queries and Hibernate Query Language (HQL, often mistyped as HSQL) for querying database records, giving developers flexibility to write database-independent or database-specific queries.

To commit a transaction in Hibernate, you must first retrieve the active transaction from the session and then call its commit method using session.getTransaction().commit(). The other options are syntactically incorrect or do not exist.

Hibernate persistent objects have three states: transient (new objects not associated with a session), persistent (associated with a session and managed), and detached (previously persistent but session closed). The 'destroyed' option is incorrect as it's not a Hibernate state.

Hibernate accepts configuration through all three methods: passing Properties directly to Configuration object, placing hibernate.properties in classpath root, or setting System properties via -D flags. This flexibility allows different deployment and configuration strategies.

All statements are true: Hibernate cannot lazily initialize associations for detached objects, accessing a lazy association outside an active session throws a LazyInitializationException, and lazy fetching avoids loading unnecessary columns or associations.

In Hibernate, createSQLQuery is used to execute native SQL queries. The correct syntax to fetch all records from a table using a native SQL query is sess.createSQLQuery("SELECT * FROM CATS").list(). HQL syntax is used in createQuery.

The cascade attribute in Hibernate mapping accepts 'all', 'persist', 'delete', and other operations like 'merge', 'save-update', 'evict', 'replicate', 'refresh', and 'delete-orphan'. These determine which operations cascade from parent to child entities.

Hibernate fully supports bi-directional associations (such as one-to-many and many-to-one) between data models, allowing navigation from either side of the relationship. This is typically configured using the mappedBy attribute.