Explore topic-wise InterviewSolutions in Current Affairs.

Named SQL QUERIES are those queries which are defined in mapping file and are called as required anywhere.
For example, we can WRITE a SQL query in our XML mapping file as follows:
[xml]
<sql-query name = “studentdetails”>
<return ALIAS=”std”/>
SELECT std.STUDENT_ID AS {std.STUDENT_ID},
std.STUDENT_DISCIPLINE AS {std.discipline},
FROM Student std WHERE std.NAME LIKE :name
</sql-query>
[/xml]
Then this query can be called as follows:
[java]
List students = session.getNamedQuery(&amp;quot;studentdetails&amp;quot;)
.setString(&amp;quot;TomBrady&amp;quot;, name)
.setMaxResults(50)
.list();
[/java]

Named SQL queries are those queries which are defined in mapping file and are called as required anywhere.
For example, we can write a SQL query in our XML mapping file as follows:
[xml]
<sql-query name = “studentdetails”>
<return alias=”std”/>
SELECT std.STUDENT_ID AS {std.STUDENT_ID},
std.STUDENT_DISCIPLINE AS {std.discipline},
FROM Student std WHERE std.NAME LIKE :name
</sql-query>
[/xml]
Then this query can be called as follows:
[java]
List students = session.getNamedQuery(&amp;quot;studentdetails&amp;quot;)
.setString(&amp;quot;TomBrady&amp;quot;, name)
.setMaxResults(50)
.list();
[/java]

Load() methods RESULTS in an EXCEPTION if the required RECORDS isn’t found in the database while GET() method returns null when records against the id isn’t found in the database.
So, ideally we should use Load() method only when we are sure about existence of records against an id.

Load() methods results in an exception if the required records isn’t found in the database while get() method returns null when records against the id isn’t found in the database.
So, ideally we should use Load() method only when we are sure about existence of records against an id.

Version property is used in HIBERNATE to know whether an OBJECT is in TRANSIENT STATE or in DETACHED state.

Version property is used in hibernate to know whether an object is in transient state or in detached state.

In ATTRIBUTE oriented programming, a developer can ADD Meta data (attributes) in the JAVA source code to add more significance in the code. For Java (hibernate), attribute oriented programming is enabled by an ENGINE called XDoclet.

In Attribute oriented programming, a developer can add Meta data (attributes) in the java source code to add more significance in the code. For Java (hibernate), attribute oriented programming is enabled by an engine called XDoclet.

session.lock() method of session class is used to REATTACH an object which has been detached earlier. This method of reattaching doesn’t CHECK for any data synchronization in DATABASE while reattaching the object and hence may lead to LACK of synchronization in data.

session.lock() method of session class is used to reattach an object which has been detached earlier. This method of reattaching doesn’t check for any data synchronization in database while reattaching the object and hence may lead to lack of synchronization in data.

Yes, HIBERNATE fully SUPPORTS polymorphism. Polymorphism QUERIES and polymorphism ASSOCIATIONS are supported in all mapping strategies of hibernate.

Yes, hibernate fully supports polymorphism. Polymorphism queries and polymorphism associations are supported in all mapping strategies of hibernate.

HIBERNATE has FOLLOWING three INHERITANCE models:
a. Tables Per CONCRETE Class
b. Table per class hierarchy
c. Table per sub-class

Hibernate has following three inheritance models:
a. Tables Per Concrete Class
b. Table per class hierarchy
c. Table per sub-class

If we don’t want an application to UPDATE or delete OBJECTS of a class in HIBERNATE, we can MAKE the class as immutable by setting mutable=false

If we don’t want an application to update or delete objects of a class in hibernate, we can make the class as immutable by setting mutable=false

GENERAL hibernate FLOW INVOLVING RDBMS is as follows:
a. Load CONFIGURATION file and CREATE object of configuration class.
b. Using configuration object, create sessionFactory object.
c. From sessionFactory, get one session.
d. Create HQL query.
e. Execute HQL query and get the results. Results will be in the form of a list.

General hibernate flow involving RDBMS is as follows:
a. Load configuration file and create object of configuration class.
b. Using configuration object, create sessionFactory object.
c. From sessionFactory, get one session.
d. Create HQL query.
e. Execute HQL query and get the results. Results will be in the form of a list.

Light Object Mapping is ONE of the levels of ORM quality in which all entities are REPRESENTED as CLASSES and they are mapped manually.

Light Object Mapping is one of the levels of ORM quality in which all entities are represented as classes and they are mapped manually.

MANAGED ASSOCIATIONS relate to container MANAGEMENT persistence and are bi-directional while HIBERNATE associations are unidirectional.

Managed associations relate to container management persistence and are bi-directional while hibernate associations are unidirectional.

Hibernate session FACTORY can be bound to JNDI by MAKING configuration CHANGES in hibernate.cfg file.

Hibernate session factory can be bound to JNDI by making configuration changes in hibernate.cfg file.

Java Applications and components are managed in HIBERNATE by a standard API CALLED JMX API. JMX provides TOOLS for development of efficient and robust distributed, web based solutions.

Java Applications and components are managed in hibernate by a standard API called JMX API. JMX provides tools for development of efficient and robust distributed, web based solutions.

With HIBERNATE 3.2, DEFAULT TRANSACTION FACTORY is JDBCTransactionFactory.

With hibernate 3.2, default transaction factory is JDBCTransactionFactory.

All the mapping between classes and tables, PROPERTIES and COLUMNS, JAVA types and SQL types ETC is defined in ORM metadata.

All the mapping between classes and tables, properties and columns, Java types and SQL types etc is defined in ORM metadata.

HIBERNATE second level cache can be disabled using any of the FOLLOWING ways:
a. By setting use_second_level_cache as false.
b. By using CACHEMODE.IGNORE
c. Using cache PROVIDER as org.hibernate.cache.NoCacheProvider

Hibernate second level cache can be disabled using any of the following ways:
a. By setting use_second_level_cache as false.
b. By using CACHEMODE.IGNORE
c. Using cache provider as org.hibernate.cache.NoCacheProvider

Objects which have been detached and are no LONGER associated with any PERSISTENT ENTITIES can be reattached by calling SESSION.merge() METHOD of session class.

Objects which have been detached and are no longer associated with any persistent entities can be reattached by calling session.merge() method of session class.

Database primary key is specified in the configuration FILE hbm.xml. GENERATOR can also be used to SPECIFY how primary key is being created in the database.
In the below example, DEPTID acts as primary key:
[xml]
<id name=”deptId” type=”STRING” >
<column name=”columnId” length=”30″/>
<generator/>
</id>
[/xml]

Database primary key is specified in the configuration file hbm.xml. Generator can also be used to specify how primary key is being created in the database.
In the below example, deptId acts as primary key:
[xml]
<id name=”deptId” type=”string” >
<column name=”columnId” length=”30″/>
<generator/>
</id>
[/xml]

Hibernate provides FOLLOWING FOUR WAYS to fetch OBJECTS from DATABASE:
a. Using HQL
b. Using identifier
c. Using Criteria API
d. Using Standard SQL

Hibernate provides following four ways to fetch objects from database:
a. Using HQL
b. Using identifier
c. Using Criteria API
d. Using Standard SQL

Hibernate Query By CRITERIA (QBC) API is used to create queries by MANIPULATION of criteria OBJECTS at RUNTIME.

Hibernate Query By Criteria (QBC) API is used to create queries by manipulation of criteria objects at runtime.

In HIBERNATE; we have FOLLOWING two TYPES of MAPPING ASSOCIATIONS between entities:
a. One-to-One Association
b. Many-to-Many Association

In hibernate; we have following two types of mapping associations between entities:
a. One-to-One Association
b. Many-to-Many Association

HIBERNATE SUPPORTS MULTIPLE cache services like EHCache, OSCache, SWARMCache and TreeCache and DEFAULT cache service of hibernate is EHCache.

Hibernate supports multiple cache services like EHCache, OSCache, SWARMCache and TreeCache and default cache service of hibernate is EHCache.

We can use any of the following two METHODS of HIBERNATE configuration:
a. XML based configuration ( using hibernate.cfg.xml FILE)
b. Programmatic configuration ( Using CODE logic)

We can use any of the following two methods of hibernate configuration:
a. XML based configuration ( using hibernate.cfg.xml file)
b. Programmatic configuration ( Using code logic)

Transaction management is the process of managing a set of statements or COMMANDS. In hibernate; transaction management is DONE by transaction interface as SHOWN in below code:
[java]
Session s = NULL;
Transaction tr = null;
try {
s = sessionFactory.openSession();
tr = s.beginTransaction();
doTheAction(s);
tr.commit();
} catch (RUNTIMEEXCEPTION exc) {
tr.rollback();
} finally {
s.close();
}
[/java]

Transaction management is the process of managing a set of statements or commands. In hibernate; transaction management is done by transaction interface as shown in below code:
[java]
Session s = null;
Transaction tr = null;
try {
s = sessionFactory.openSession();
tr = s.beginTransaction();
doTheAction(s);
tr.commit();
} catch (RuntimeException exc) {
tr.rollback();
} finally {
s.close();
}
[/java]

FOLLOWING are the four ORM LEVELS in hibernate:
a. PURE Relational
b. Light Object Mapping
c. MEDIUM Object Mapping
d. Full Object Mapping

Following are the four ORM levels in hibernate:
a. Pure Relational
b. Light Object Mapping
c. Medium Object Mapping
d. Full Object Mapping

When an instance was earlier associated with some PERSISTENT CONTEXT (e.g. a table) and is no LONGER associated, it’s called to be in DETACHED state.

When an instance was earlier associated with some persistent context (e.g. a table) and is no longer associated, it’s called to be in detached state.

CALLBACK INTERFACES of hibernate are useful in receiving event notifications from objects. For example, when an object is loaded or deleted, an event is GENERATED and NOTIFICATION is sent using callback interfaces.

Callback interfaces of hibernate are useful in receiving event notifications from objects. For example, when an object is loaded or deleted, an event is generated and notification is sent using callback interfaces.

HIBERNATE provides dirty checking feature which can be USED to reduce database WRITE times. Dirty checking feature of hibernate UPDATES only those fields which require a CHANGE while keeps others unchanged.

Hibernate provides dirty checking feature which can be used to reduce database write times. Dirty checking feature of hibernate updates only those fields which require a change while keeps others unchanged.

If an instance is not ASSOCIATED with any PERSISTENT context and also, it has NEVER been associated with any persistent context, then it’s said to be in TRANSIENT STATE.

If an instance is not associated with any persistent context and also, it has never been associated with any persistent context, then it’s said to be in transient state.

We can get hibernate STATISTICS USING getStatistics() method of SessionFactory CLASS as SHOWN below:
SessionFactory.getStatistics()

We can get hibernate statistics using getStatistics() method of SessionFactory class as shown below:
SessionFactory.getStatistics()

a.Hibernate can be used seamlessly with any TYPE of database as its database independent while in CASE of JDBC, developer has to write database specific queries.
b. Using hibernate, developer doesn’t NEED to be an expert of writing complex queries as HQL simplifies query writing process while in case of JDBC, its JOB of developer to write and tune queries.
c. In case of hibernate, there is no need to create connection pools as hibernate does all connection handling automatically while in case of JDBC, connection pools need to be created.

a.Hibernate can be used seamlessly with any type of database as its database independent while in case of JDBC, developer has to write database specific queries.
b. Using hibernate, developer doesn’t need to be an expert of writing complex queries as HQL simplifies query writing process while in case of JDBC, its job of developer to write and tune queries.
c. In case of hibernate, there is no need to create connection pools as hibernate does all connection handling automatically while in case of JDBC, connection pools need to be created.

Sessionsave() method SAVES a RECORD only if it’s unique with RESPECT to its primary key and will FAIL to insert if primary key already EXISTS in the table.
saveOrUpdate() method inserts a new record if primary key is unique and will update an existing record if primary key exists in the table already.

Sessionsave() method saves a record only if it’s unique with respect to its primary key and will fail to insert if primary key already exists in the table.
saveOrUpdate() method inserts a new record if primary key is unique and will update an existing record if primary key exists in the table already.

Following are the TWO TYPES of COLLECTIONS in hibernate:
a. SORTED Collection
b. Order Collection

Following are the two types of collections in hibernate:
a. Sorted Collection
b. Order Collection

We need to add following in HIBERNATE configuration file to ENABLE viewing SQL on the console for debugging PURPOSES:
[XML]
&LT;property name=”show_sql”>true</property>
[/xml]

We need to add following in hibernate configuration file to enable viewing SQL on the console for debugging purposes:
[xml]
<property name=”show_sql”>true</property>
[/xml]

Following are some key BENEFITS of USING Hibernate TEMPLATE:
a. Session closing is automated.
b. Interaction with hibernate session is simplified.
c. EXCEPTION handling is automated.

Following are some key benefits of using Hibernate template:
a. Session closing is automated.
b. Interaction with hibernate session is simplified.
c. Exception handling is automated.

CRITERIA is a SIMPLE YET powerful API of hibernate which is USED to retrieve entities through criteria OBJECT composition.

Criteria is a simple yet powerful API of hibernate which is used to retrieve entities through criteria object composition.

In HIBERNATE we can EXECUTE STORED procedures using code as below:
[xml]
<sql-query NAME=”getStudents” callable=”true”>
<return alias=”st” class=”Student”>
<return-property name=”std_id” column=”STD_ID”/>
<return-property name=”s_name” column=”STD_NAME”/>
<return-property name=”s_dept” column=”STD_DEPARTMENT”/>
{ ? = call selectStudents() }
</return>
</sql-query>
[/xml]

In hibernate we can execute stored procedures using code as below:
[xml]
<sql-query name=”getStudents” callable=”true”>
<return alias=”st” class=”Student”>
<return-property name=”std_id” column=”STD_ID”/>
<return-property name=”s_name” column=”STD_NAME”/>
<return-property name=”s_dept” column=”STD_DEPARTMENT”/>
{ ? = call selectStudents() }
</return>
</sql-query>
[/xml]

HQL is the QUERY language USED in HIBERNATE which is an EXTENSION of SQL. HQL is very efficient, simple and FLEXIBLE query language to do various type of operations on relational database without writing complex database queries.

HQL is the query language used in Hibernate which is an extension of SQL. HQL is very efficient, simple and flexible query language to do various type of operations on relational database without writing complex database queries.

POJOS( Plain Old Java Objects) are java BEANS with proper getter and setter methods for each and every properties.
Use of POJOs instead of simple java classes RESULTS in an efficient and well CONSTRUCTED code.

POJOs( Plain Old Java Objects) are java beans with proper getter and setter methods for each and every properties.
Use of POJOs instead of simple java classes results in an efficient and well constructed code.

To CREATE a session factory in hibernate, an OBJECT of CONFIGURATION is CREATED first which refers to the path of configuration file and then for that configuration, session factory is created as given in the EXAMPLE below:

1. configuration config = new Configuration();
2. config.addResource(&amp;amp;quot;myinstance/configuration.hbm.xml&amp;amp;quot;);
3. config.setProperties( System.getProperties() );
4. SessionFactory sessions = config.buildSessionFactory();

To create a session factory in hibernate, an object of configuration is created first which refers to the path of configuration file and then for that configuration, session factory is created as given in the example below:

No, having .hbm.xml extension is a convention and not a REQUIREMENT for HIBERNATE MAPPING FILE names. We can have any extension for these mapping files.

No, having .hbm.xml extension is a convention and not a requirement for hibernate mapping file names. We can have any extension for these mapping files.

We can use EXTENSION interfaces in ORDER to add any REQUIRED FUNCTIONALITY which isn’t SUPPORTED by built-in interfaces.

We can use extension interfaces in order to add any required functionality which isn’t supported by built-in interfaces.

Configuration interface of HIBERNATE FRAMEWORK is USED to configure hibernate. It’s ALSO used to bootstrap hibernate. Mapping documents of hibernate are LOCATED using this interface.

Configuration interface of hibernate framework is used to configure hibernate. It’s also used to bootstrap hibernate. Mapping documents of hibernate are located using this interface.

HIBERNATE is a POPULAR framework of JAVA which allows an efficient Object Relational MAPPING using configuration FILES in XML format. After java objects mapping to database tables, database is used and handled using Java objects without writing complex database queries.

Hibernate is a popular framework of Java which allows an efficient Object Relational mapping using configuration files in XML format. After java objects mapping to database tables, database is used and handled using Java objects without writing complex database queries.