The delete trigger needs no exception handling.
删除触发器不需要异常处理。
As before, the delete trigger needs no modification.
与以前一样，删除触发器不需要修改。
The delete trigger does not depend on the coordinate values, so nothing changes there.
删除触发器不依赖于坐标值，所以这里不需要修改。
The new table 'test'. '_online_table_new' does not have a PRIMARY KEY or a unique index which is required for the DELETE trigger.
原表需要一个主键或则唯一索引，因为删除的触发器需要，否则数据不会被复制。
Listing 10 shows one approach, which is to bind the "Delete" trigger to a node in the data model, and then to make that node non-relevant when the count of nodes in the set reaches 1.
清单10给出了一种方法，那就是将“删除”触发器绑定到数据模型中的节点上，然后在节点集中的节点数达到1时使该节点变为不相关。
This means that the actions of create profile, delete profile, add node, remove node, should also trigger a snapshot to the installation data.
这意味着，创建概要、删除概要、添加节点、删除节点操作均应触发安装数据的快照捕获。
In trigger terminology, the INSERT, DELETE, or UPDATE that causes a trigger to be fired is known as the triggering event.
在触发器术语中，INSERT、DELETE或者UPDATE这些使得触发器启动的事件被称作触发事件。
Delete the following line from the trigger handler.
删除触发器处理程序中的下列代码行。
In addition, triggers can now contain UPDATE, DELETE, and INSERT operations together in a single clause as the trigger event. For example.
另外，触发器现在可以在单一子句中同时包含UPDATE、DELETE和INSERT操作，作为一个触发器事件。
If there were a trigger, for example, you would see that reflected in one or more additional insert, Update, or Delete entries in the access plan.
例如，如果有一个触发器的话，那么就会在访问计划中的一个或多个insert、Update或Delete条目中反映出来。
When a specified SQL operation — a DELETE, INSERT, or UPDATE — occurs on a table, a trigger can be activated that defines a set of actions.
当一个指定的SQL操作(如DELETE,INSERT，或者是UPDATE操作)作用于某张表时，一个定义了一组操作的触发器就可以被激活。
In the update trigger, you need to delete the corresponding feature if one of the coordinates becomes null.
在更新触发器中，如果坐标值之一变成null，那么需要删除对应的特性。
The update trigger is more complicated: if the update causes an exception, you have to delete the existing feature row, just as for null coordinates.
更新触发器比较复杂：如果更新导致异常，那么必须删除现有的特性行，就像处理null坐标一样。
This usually works fine, but if you have has_many relationships defined, you may trigger a cascading delete.
这通常会出色地完成，但是如果您定义了has_many关系，则有可能会触发级联(cascading)删除。
The author of Class::DBI has promised a standard solution for this that will allow the programmer to specify that a has_many() relationship should not trigger a cascading delete.
DBI的作者已经承诺要为此提出一个标准的解决方案，让程序员可以指定某个 has_many()关系不应触发级联删除。
By monitoring single or multiple create, open, update, or delete events to the Notes documents, Virtual Field activities trigger the appropriate result in the external system data.
通过监控Notes文档的单个或多个创建、打开、更新或删除事件，VirtualField活动在外部系统数据中触发适当的结果。
For example, let's say you chose a Time to trigger action of Before for an trigger that is fired by a DELETE statement.
例如，假设您的触发器选择的Timeto triggeraction是Before，触发事件是delete语句。
It is a common practice to put a pre-operation trigger for the Rational ClearCase Rmname operation to ensure that no one is able to delete any artifact (UN) intentionally.
对于RationalClearCaseRmname操作有一个预操作激发器的一般实践行为，以确保没人能够有意地删除一个工件(un)。
Specified delete rule not allowed with existing trigger.
说明：指定删除不与现有触发器允许的规则。
If you try to delete rows from such a table, the trigger rolls back the delete.
如果尝试删除这类表中的行，该触发器将回滚删除操作。
If you try to delete rows from such a table, the trigger rolls back the delete action.
如果您尝试删除此类表中的行，该触发器将回滚删除操作。
If you try to delete rows from such a table, the trigger rolls back the delete action.
如果您尝试删除此类表中的行，该触发器将回滚删除操作。
应用推荐