This is done using database triggers.
这要使用数据库触发器来完成。
You'll define database triggers for the JDBC adapter inbound processing.
您需要为JDBC适配器入站处理定义数据库触发器。
The event store table gets populated when one of the database triggers runs.
当其中一个数据库触发器运行时，将填充事件存储表。
An event table stores the asynchronous events generated by the database triggers in a staging table.
事件表存储数据库触发器在分段表中生成的异步事件。
A big problem with database triggers is that the application does not know that they exist, therefore does not know whether they have run or not.
应用程序是感知不到触发器的存在的，因此也不知道他们运行了还是没有，这是一个大问题。
Optimistic locking will not work if Hibernate is not the sole database user, unless you create database triggers to increment the version column for the same data change by other applications.
如果Hibernate不是独占数据库用户，乐观锁会失效，除非创建数据库触发器为其他应用程序对相同数据的变更增加版本字段值。
Optimistic locking will not work if Hibernate is not the sole database user, unless you create database triggers to increment the version column for the same data change by other applications.
如果Hibernate不是独占数据库用户，乐观锁会失效，除非创建数据库触发器为其他应用程序对相同数据的变更增加版本字段值。
应用推荐