Another way to implement soft delete is with an interceptor.

I tried this method first but got into trouble when having catalog prefix before my table name.

What I did instead was to implement a SoftDeleteInterceptor that intercepted the prepared stmt and modified it to an update stmt.

This will of course make it impossible to delete anything, but if that is the preferred behaviour it will work.

public class SoftDeleteInterceptor extends EmptyInterceptor {

private static final long serialVersionUID = 1L;

@Override
public String onPrepareStatement(String sql) {
System.err.println(sql);
if (sql.startsWith(“delete from”)) {
String softDeleteSql = sql.replace(“delete from”, “update”).replace(“where”, “set c_rcd_del = ‘Y’ where”);
return super.onPrepareStatement(softDeleteSql);
}
return super.onPrepareStatement(sql);
}

}

To activate the interceptor add the following to persistence.xml

Great post! Thanks for the information.

I was wondering if there is anyway to use the @SQLDelete in a generic way so that I could use it in a mapped superclass?

I have a base entity that I want to use for all my entities, and I need the soft delete for each as well. I was hoping there was a way to setup the query so that it updates the correct table.

Thanks,
John