Refreshing database

[charlscross]

When I'm doing query's with a conversation scoped entitymanager, if other application changes the database, my entityManager doesn't notices this changes until I create a new conversation. I thought that doing a flush I could get the changes, but it doesn't work. Is there any instruction for doing this syncronizing??

This is my persistence unit:

<persistence-unit name="SistemaMonitorizacion">
      <provider>org.hibernate.ejb.HibernatePersistence</provider>
      <jta-data-source>java:/SistemaMonitorizacionDatasource</jta-data-source>
      <properties>
         <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
         <property name="hibernate.hbm2ddl.auto" value="validate"/>
         <property name="hibernate.show_sql" value="true"/>
         <property name="hibernate.format_sql" value="true"/>
         <property name="jboss.entity.manager.factory.jndi.name" value="java:/SistemaMonitorizacionEntityManagerFactory"/>
      </properties>
   </persistence-unit>

Thanks!!

[joblini]

Hi Charls,

You can refresh a single entity like this

getEntityManager().refresh(getInstance());

Or, you can close the entity manager

getEntityManager().close()

The next call to getEntityManager() should return a fresh instance.

See the org.jboss.seam.framework.EntityController class, also, refer to
Hibernate Entity Manager

[kapitanpetko]

If it is a simple query the get a list of entities, the easiest thing would be to call
entityManager.clear() before you issue the query. Depending on how many entities the
query returns, that might be quite slow, so use with caution :) It could also break stuff
in other tabs, if you are using lazy relationships.

[charlscross]

Thanks you both!!

[joblini]

Hmmm, interestingly, the Hibernate Entity Manager documentation states that a flush will be automatically performed, and the state synchronized with the database, before query execution.  It does specify that a transaction must be active, perhaps that is something you could check.

See this post:

WhyEjbFunctionIsTryingToFlush

[joblini]

I think that, in this case, synchronization with the data store means writing out changes, not refreshing entities.