I tried to refactor an existing application and start using hibernate. The current application use oracle sequence to generate the pk for a few tables. The way it does is to use the insert trigger to generate the id.

When I use the
<id name="id">
<generator class="sequence"/>
<param>sq_lms_incident</param>
</id>

do I need to remove the trigger from the database? Or do we have a way to work around so that we still can continue using the existing trigger?

How does it work? Is it that hibernate first issue a sql to get an id from oracle sequence, populate the class id property and then issue another sql to insert all persistent the properties to the table including the id field?

Qin

Yes, that is the way it works. If you have an autogenerated id, you could probably work around it by using the "identity" generator, and create a subclass of the dialect you use. Then override getIdentitySelectString() to return the SQL query needed to retrieve the last generated id.

Gloeglm:

I don't follow what you said:

"create a subclass of the dialect you use. Then override getIdentitySelectString() to return the SQL query needed to retrieve the last generated id." Would you please explain? Thanks.

Hm, well, create a class extending the dialect class you use for hibernate, override getIdentitySelectString() to return an SQL query needed to select your last generated id. Then use this class as dialect.