Answer / imambasha

caching concept in hibernate is performed internally in
stages...
1)firstlevel(Session) caching
2)Secondlevel(SessionFactory) caching
1)firstlevel(Session) caching:
First-level cache always Associates with the Session
object. Hibernate uses this cache by default. Here, it
processes one transaction after another one, means wont
process one transaction many times. Mainly it reduces the
number of SQL queries it needs to generate within a given
transaction. That is instead of updating after every
modification done in the transaction, it updates the
transaction only at the end of the transaction.

2)Secondlevel(SessionFactory) caching
Second-level cache always associates with the Session
Factory object. While running the transactions, in between
it loads the objects at the Session Factory level, so that
those objects will available to the entire application,
don’t bounds to single user. Since the objects are already
loaded in the cache, whenever an object is returned by the
query, at that time no need to go for a database
transaction. In this way the second level cache works.

int x=5,i=1,y=0; while(i<=5) { y=x++ + ++x; i=i+2; } System.out.println(x); System.out.println(y); System.out.println(i); How to solve this? Please explain!

0 Answers  

---

function of extends and implements keywords?

2 Answers  

---

What is a clone?

0 Answers  

---

What’s jboss cache in short?

0 Answers  

---

How do u supress the parameters from the displaying in the url?

2 Answers  

---

What is thread deadlock? How to resolve thread deadlock?

3 Answers  

---

Name the class that is used to bind the server object with RMI Registry?

0 Answers  

---

how can we load a file of a user in the database table?

3 Answers   ITC Infotech,

---

What is Bootstrapping in RMI?

1 Answers  

---

how to get value in combo for updation?

1 Answers   CMC,

---

What is Stream and Types?

2 Answers   Patni,

---

Why does the option tag render selected=selected instead of just selected?

0 Answers  

---