Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version:
3.0.5

Mapping documents:
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping>
<class name="com.siemens.swa.domain.DistributionCenterSTC"
table="DISTRIBUTION_CENTER_STC"
dynamic-update="false"
dynamic-insert="false"
select-before-update="false"
optimistic-lock="version"
lazy="true"
batch-size="6">

<id
name="id"
column="DISTRIBUTION_CENTER_STC_ID"
type="java.lang.Long"
>
<generator class="native"/>
</id>

<property
name="modemModelSeries"
column="MODEM_MODEL_SERIES"
not-null="true"
type="java.lang.String"
unique="true"
/>

<property
name="inclusionDate"
column="INCLUSION_DATE"
not-null="true"
type="java.util.Calendar"
/>

<property
name="matricula"
column="MATRICULA"
type="java.lang.String"
/>

<property
name="action"
column="ACTION"
not-null="true"
type="java.lang.String"
/>

<property
name="stcMovementStatus"
column="STC_MOVEMENT_STATUS"
type="java.lang.Integer"
/>

<property
name="stcOperationStatus"
column="STC_OPERATION_STATUS"
type="java.lang.Integer"
/>

<property
name="dateUpdated"
column="DATE_UPDATED"
type="java.util.Calendar"
/>

</class>
</hibernate-mapping>


Code between sessionFactory.openSession() and session.close():
n/a
Full stack trace of any exception that occurs:
n/a

Name and version of the database you are using:
MySQL 4.1.15

The generated SQL (show_sql=true):
n/a

Debug level Hibernate log excerpt:
n/a

Hi all,

We have an existing Hibernate app. We have a new requirement to implement a table that can be written to by Hibernate AND another, non java/hibernate application.

My understanding is that Hibernate SessionFactory relies on the assumption that it's the only entity accesing the database. How can I allow another application to write to this database table - which maps to the hbm file above?

I'm under the impression that having a 'serializable transaction' isolation level set at the mysql level may help. However, we are _NOT_ running innodb. We have plans to migrate to mysql 5.0 .

Any help appreciated,
iksrazal

You should read about locking strategies in the reference and versioning

You should trust your session very little. You may consider to lock objects when you update them.

You should analyse your application to find out specific situations, where concurrency can be a problem.

serializable transaction could bring your dead locks and performance problems.

Sebastian