Hibernate Interview Questions Answers
Hibernate Interview Questions Answers
Hibernate Interview Questions Answers
Hibernate is an ORM (object-relational mapping ) tool for Java programming language. It is developed by Red
Hat and was started by Gavin King with his colleagues in 2001. The original aim was to offer better persistence
capabilities than those offered by EJB2 (Enterprise Java Beans version 2), they wanted to simplify the
complexities and supplement certain missing features.
Below we have provided hibernate Interview questions are specifically designed to give you the basic
conceptual information at the beginning and later with the core nature of the subject. The information which has
been provided will brush up your mind and will substantially contribute to impressing the interviewer so that
you fly with high colors.
Hibernate is a free software, which is distributed under GNU Lesser General public license 2.1.
It is categorized under the Object Relational Mapping (ORM), which features the mapping of Java classes
to data tables and mapping from Java data types to SQL data types.
It is written in Java and is JVM (Java Virtual Machine) platform based.
Hibernate provides the data query and retrieval facilities.
It is one of the most widely used ORM tools for the Java applications.
Hibernate is highly considered to be used in the enterprise applications for database operations.
HQL is the acronym of Hibernate Query Language.It considers the java objects in a similar way as that of the
SQL.
It is an Object-Oriented Query Language and is independent of the database.
It allows business code access the objects rather than Database tables.
It hides the details of SQL queries from OO logic.
It is based on JDBC “under hood”.
Dealing with database implementation is not required.
Entities are based on business concepts rather than database structures.
It generates the automatic key and Transaction management.
Application development is faster.
It is used to get a physical connection with a database. A session object is designed to instantiate each time an
interaction is required with the database, whereas the persistent objects are retrieved using a session object.
The session objects are not thread-safe and must be created and destroyed as per the requirement.
It represents a unit of work with the database and most of the RDBMS (Relational Database Management
System) supports transaction functionality.
In Hibernate, transactions are managed by an underlying transaction manager and transaction from JDBC or
JTA.
It is an optional object and the Hibernate Application do not use this interface, instead, they handle the
transactions in their code.
These objects use SQL and HQL string to retrieve data from the database and create objects.
An instance of Query is used to bind query parameters, restrict the number of results returned by the query and
finally to execute the query.
Hibernate supports all the major RDMS.Following are the list of database engines supported by Hibernate:
HSQL Database Engine
DB2/NT
Oracle
Microsoft SQL Server Database
Sybase SQL Server
Informix Dynamic Server
MySQL
PostgreSQL
FrontBase
It is similar to the many-to-one association and the difference lies in the column that will be set as a unique
one.The many-to-one element is used to define one-to-one association.
To the defined variable a name attribute is set in the parent class and the column attribute is used to set column
name in the parent table, which is unique so that only one object gets associated with another.
This association is the common type of association where one object can be associated with multiple objects.
And Many-to-one element defines the Many-to-One association.To the defined variable, a name attribute is set
in the parent class and column attribute sets the column name in the parent table.
Q14. What is Many-to-Many association in Hibernate?
The Many-to-Many element indicates the relation between one object to many other objects and column
attribute is used to link intermediate columns. A Many-to-Many mapping is implemented using a Set Java
collection that does not have any redundant element.
Hibernate caches Query data and makes the application run faster.
If used correctly, the hibernate cache can be very useful in achieving the faster application running performance.
The main idea lying behind the cache is reducing the number of database queries, which results in reduced
throughput time of the application.
It is session cache and mandatory cache. It is from first level cache through which all the requests must pass.The
session object stores an object under its control before committing it to the database.
It is an optional cache. And, always the first level cache will be consulted before any attempt is performed to
locate an object in the second level cache. This cache can be configured on a pre-collection and per-class basis
and it is mainly responsible for caching objects across the sessions.
In hibernate, a cache query can be implemented that results in sets and integrates closely with the second level
cache.It is an optional feature and it requires two additional cache regions that can hold the cached query results
and also the timestamps whenever a table is updated. This is useful only for the queries that run frequently
holding the same parameters.
The concurrency strategies are the mediators who are responsible for storing items and retrieving them from the
cache.In case of enabling a second level cache, the developer must decide for each persistent class and
collection, and also which cache concurrency, has to be implemented.
Following are the concurrency strategies that can be implemented by the developer:
Transactional: This strategy is used mostly to read data where the prevention of stale data is critical in
concurrent transactions, in the unique case of an update.
Read- Only: This strategy is compatible with the data that can’t be modified. We can use it for reference
data only.
Read-Write: It is similar to transactional strategy. where we read mostly data and prevention of stale data
is critical.
Non-strict-Read-Write: This strategy assures no guarantee of consistency between the database and
cache. We can use this strategy only if the data can be modified and a small likelihood of stale data is not
the critical concern.
It is a technique in where the objects are loaded on the requirement basis. Since the Hibernate 3 version, the
lazy loading is by default enabled so that the child objects are not loaded while the parent is loaded.
In hibernate, the Java classes whose instances and objects are stored in database classes are called persistent
classes.
Q24. Describe the method used to create an HQL Query and SQL Query?
Session.createQuery is used to create a new instance of a query for the HQL query string.
Session.createSQLQuery is used to create a new instance of a query for the SQL query string.
On the whole, hibernate makes it a better choice in the current market for ORM tool, as it contains all the
features that you will require in an ORM tool.
SessionFactory (org.hibernate.SessionFactory)
It is an immutable thread safe cache of compiled mappings for a single database.
We are supposed to initialize SessionFactory once and then we are allowed to cache and reuse it.
The SessionFactory instance is used to return the session objects for database operations.
Session (org.hibernate.Session)
It is a single threaded and short-lived object, which represents a conversation between the persistent store
and the application.
The session should be opened only when it is required and should be closed as soon as the user is done.
The session object is the interface between hibernate framework and Java application code and it provides
methods for the CRUD operations.
Transaction (org.hibernate.transaction)
It is a single threaded and short-lived object used by the application, which specifies atomic units of work.
The application is abstracted from the underlying JDBC or JTA transaction.
Example
@Entity
@Table(name="posts")
public class Post{
String title;
String description;
}
Q33. How to create two same tables in different Schema’s by using single configuration
file?
Conclusion
So, these were some of the Hibernate Interview questions that can be asked to you during an interview. It is
alright if you were not able to answer a few questions, but make sure that you face it with confidence. Have a
glance at these questions and get ready to crack it!!