Rule Definition
Triggers and object-relational mapping often create issues due to the difficulties of synchronizing the effect of a trigger with the representation of data in memory. To enhance performances, it is a best practice to use the attribute select-before-update for the persistent class associated to a table that have the UPDATE trigger. But if the table is not associated to an UPDATE trigger, then it will affect your performance since the application will perform unnecessary SELECT.

Remediation
Remove the attribute select-before-update for the persistent class that is not associated to a table that have the UPDATE trigger.

Violation Code Sample

SAMPLE is a table not managed by an UPDATE trigger
---> sample.hbm.xml
// VIOLATION
<class name="Sample" table="SAMPLE" select-before-update="true">
...
</class>



---> sample.java

@org.hibernate.annotations.Entity(
        selectBeforeUpdate = true, ...)
@org.hibernate.annotations.Table(name="SAMPLE")
public class Sample{ ... }

---> sample2.java

@Entity(name = "SAMPLE")
@Table(name = "SAMPLE")
@SelectBeforeUpdate
public class Sample{
 //...
}

Fixed Code Sample

---> sample.hbm.xml
// VIOLATION
<class name="Sample" table="SAMPLE">
...
</class>



---> sample.java
@Entity
@org.hibernate.annotations.Table(name="SAMPLE")
public class Sample{ ... }

Hibernate in Action (ISBN 1932394-15-X) p 339 https://docs.jboss.org/hibernate/orm/3.5/reference/en/html/mapping.html