Column3只是显示日程表事件的文本值。
Column3 simply displays the text value for the calendar event.
表的行和列代表事件和状态，单元格内包含动作和转移。
Rows and columns represent events and states, and cells contain actions and transitions.
这样可以突出条目，帮助用户在视图中找到日程表事件。
This will highlight the entry and help users locate calendar events in the view.
第一种方法是管理连续日程表事件的一种简单而有效的方法。
This first approach is a simple and efficient method to manage sequential calendar events.
最外层的元素包括一个或多个元素，分别对应一个日程表事件。
The outermost element encloses one or more elements, each representing a calendar event.
如果是正数，则将日程表事件显示到起始日期的右边(或将来)。
Positive Numbers will display calendar events to the right (or future) of the start date.
如果是负数，则将日程表事件显示到起始日期的左边(或之前)。
Negative Numbers will display calendar events to the left (or prior) to the start date.
在上传、处理或显示日程表事件的某个时刻，会丢失一些原始格式。
At some point during the upload, processing, or display of a calendar event, some of the original formatting is lost.
由于每个事件都是作为惟一的文档存放的，因此用户可以在不影响其他相关事件的情况下移动、删除或更新一个日程表事件。
Since each event is stored as a unique document, users can move, delete or update one calendar event without affecting the other related events.
要真正响应事件，必须在实现文件内定义事件表。
To actually respond to events, you must define the event table within your implementation files.
事件表档案文件视图(图7a)包含关于已经处理的事件的信息。
The event table archive view (Figure 7a) contains information about the events that have been processed.
元表的键值称为事件；值（换而言之就是函数）称为元方法。
The keys of the metatable are called events; the values (in other words, the functions) are called metamethods.
交付失败的事件将在事件库表的 “Event_Status”列中标记为 “-1”。
The events that failed to deliver are marked as “-1” in the column name “Event_Status” of the event store table.
表3：neworder事件组的配置设置值。
Table 3: Configuration Settings for the NewOrder event group.
图5举例说明了适配器和应用程序事件表之间的交互。
Figure 5 illustrates the interaction between an adapter and an application event table.
表2展示了这些事件的一些详细信息。
图6显示了运行数据库创建脚本后的事件存储表。
Figure 6 shows the event store table after running the database creation scripts.
通过避免收集不必要的事件表和字段，对性能的影响即可降低到最低限度。
By excluding unnecessary event tables and fields from being collected, performance impact can be minimized.
该小部件还发布表1中列示的事件。
您可以用类似的方式装载用于其他事件类型的表。
You can load the tables for the other event types in a similar way.
对源表的更改或事件从日志中进行捕获，并转换为xml格式的消息。
Changes to source tables, or events, are captured from the log and converted to messages in an XML format.
当其中一个数据库触发器运行时，将填充事件存储表。
The event store table gets populated when one of the database triggers runs.
比方说，可以编写一个模块读取数据库表并输出SAX事件流。
You can for example write a module that reads a table in a database and outputs a stream of SAX events.
例如，对于JDBC适配器，此队列将为“事件表”，而对于MQ适配器，此队列将为一个mq队列。
For example, in the case of the JDBC adapter, this queue will be the "event table", and in the case of the MQ adapter, this queue will be an MQ queue.
IBMTSOM使用范围分区实现事件表，所以您可以分离一个分区，将分离的分区保存在一个外部存储上，或者删除所分离的分区。
IBM TSOM USES range partitioning for event tables, so you can detach a partition, archive the detached partition on an external storage, or drop the detached partition.
要从croton_data表中检索单个事件报告，只需一个XML查询即可。
TO retrieve a single incident report from the CROTON_DATA table requires just an XML query. Listing 4 illustrates an example query.
CPTableView的代理上定义了几个方法，每个方法都对应一个数据表可以发起的事件。
Several different methods are defined on the CPTableView's delegate. Each of these corresponds to an event that can be raised by the table.
表2列出了最有用的事件和过滤器。
数据库触发器是驻留在数据库中的程序，当数据库中的表发生更新之类的事件时会运行该触发器。
A database trigger is program residing in the database that runs when an event, such as an update, occurs on a table in the database.
可以通过编写脚本来使用DB 2WorkloadManager (WLM)，从而调用表函数、存储过程和事件监视器，收集关于工作负载的信息。
You can use DB2 workload Manager (WLM) by writing your own scripts to call the table functions, stored procedures, and event monitors to gather information about the workload.
应用推荐