How can I just flush one entity, so it's can be queried before commit, which will flush everything.

I konw createSQLQuery can do this, but is there any more convenience methods available?

example:(What I want is 'tela' can be query in same Transaction it's saved. Can't flush everything, the Transaction have other things to do.)
session.beginTransaction();
TTelephone tela = new TTelephone();
tela.setCitycode("jx");
tela.setAreaCode("0573");
tela.setTelephone("0000");
tela.setAddress("tela");
session.save(tela);

TTelephone telb = telephoneDao.findByTel("0000").get(0);
System.out.println(tela);
System.out.println(telb);
System.out.println(tela == telb);
session.getTransaction().rollback();

use session.evict() method for flushing only one entity or entity collection.

for er.,

session.evict(Users.class);

u can also use sessionFactory for this...

sessionFactory.evict(Users.class);

Changes to the instance will not be synchronized with the database

/**
* Remove this instance from the session cache. Changes to the instance will
* not be synchronized with the database. This operation cascades to associated
* instances if the association is mapped with <tt>cascade="evict"</tt>.
*
* @param object a persistent instance
* @throws HibernateException
*/
public void evict(Object object) throws HibernateException;

ur requirement is to get latest data from DB. is it?

if ur answer is yes then, use evict() method.


*) i can't understand ur quest.

i dont think so its a good idea

there is no methods to flush() single entity. so use evict() to remove instance from cache and then when will u query it returns new data (i.e., hit from DB not from cache).

i m used this technique in my project, i works fine.


u may also use refresh() ..

void refresh(Object object)
--- Re-read the state of the given instance from the underlying database.

where object in this method, use ur entity.

But it will not work for neoscript since it is a new entity that is scheduled for insertion with session.save(). There is no information in the database about this object.



As far as I know this is correct. A flush() always flushes everything.

However I know that Session.save() does an immediate insert with some identifier generators (eg. those that depend on the database for generating the ID). But it also seems like there is going to be some changes with respect to this in Hibernate 3.4 (http://opensource.atlassian.com/project ... e/HHH-2439)

Why is it not possible to insert the newly created entity in another transaction? This would be the normal solution. What if your "big" transaction is rolled back? Should the newly created instances, which you want to be saved immediately, be deleted?