Finally, the team needed to assemble everything into a table and update the events table with the depot location name or null. The full SQL is.
最后，该团队需要将每项数据组装到一个表中，使用维修站位置、名称或null更新事件表。
Table 2 shows the details of some of these events.
表2展示了这些事件的一些详细信息。
Table 1 lists the different types of database events that can be audited and describes when an audit record is generated.
表1列出了可以审计的不同类型的数据库事件，并描述了审计记录是何时生成的。
The event monitor fetches event data from the event queue table based on the configuration data, converts the events into JMS messages, and puts the JMS messages on a JMS event queue.
事件监视器能根据配置数据从事件队列表取出事件数据，将事件转换成JMS消息，然后将 JMS 消息放回到一个 JMS 事件队列中。
You can edit the state chart to add and delete transitions and events, and you can switch between the diagram and the table view of the state chart.
您可以编辑状态表，以添加和删除过渡和事件，您可以在状态图的图表和表格视图之间进行切换。
You implemented your state table as a common handler for all events, plus a function array for all actions and transitions.
将状态表实现为适用于所有事件的通用处理函数，并为所有操作和转换提供一个函数数组。
Empty table cells indicate events that should not occur in particular states.
空的表单元格表示在特定状态下不应该发生特定的事件。
Application events are typically stored in an event table containing information about the sequences of events that occurred in an application, rather than the data associated with the event.
应用程序事件一般存储在一个事件表中，这个表包含着与应用程序中发生的事件的顺序有关的信息而不是与事件有关的数据。
The logged events are placed into an event queue table in the library server database.
所记录的事件会被记录到库服务器数据库的一个事件队列表中。
In the following table, you can see how these events are collected.
在下表中，可以看到如何收集这些事件。
The profiling table provides the percentage and number of samples collected for specified processor events such as the number of cache line misses, Transition Lookaside Buffer (TLB) misses, and so on.
评测表提供为特定的处理器事件收集的采样的百分数或数量，比如高速缓存线路故障的数量、传输后备缓存(TLB)故障的数量，等等。
HTTP methods are mapped into collection and member events, as shown in Table 2.
HTTP方法将映射到集合和成员事件，如表2所示。
A more elegant solution would be to use an additional table to represent the relationship between events and clients.
更好的解决方案是使用另一个表来表示事件和客户之间的关系。
The widget also publishes the events listed in the Table 1.
该小部件还发布表1中列示的事件。
The following table provides a summary of the process choreographer audit events.
以下表格提供了流程编排器审核事件的概述。
To actually respond to events, you must define the event table within your implementation files.
要真正响应事件，必须在实现文件内定义事件表。
In the table, it stores both events to be delivered and failed delivery events.
表中存储了待交付的事件以及失败的交付事件。
The figure shows an archive table that archives processed events and an event staging table that stores events that require reprocessing.
图中显示了一个档案文件表，它存储处理过的事件，还有一个事件阶段表，它存储需要再处理的事件。
An event table stores the asynchronous events generated by the database triggers in a staging table.
事件表存储数据库触发器在分段表中生成的异步事件。
This table could continue to grow, depending on the number of events received with contexts, ultimately resulting in poor performance.
根据接收的事件数量，这个表会不断增长，最终导致性能变差。
This database includes the Customer table, which is the table that the application will synchronize, and the event table that the JDBC resource adapter will poll to create inbound events.
此数据库包括应用程序将要同步的客户表和JDBC资源适配器将轮询以创建入站事件的事件表。
You can for example write a module that reads a table in a database and outputs a stream of SAX events.
比方说，可以编写一个模块读取数据库表并输出SAX事件流。
The rows and columns of the state table are labeled with the names of the events that the widget will respond to, and the states the widget will wait in between events.
状态表的行和列标上了部件要响应的事件的名称，以及在事件之间部件所处的状态。
Table 2 summarizes the most useful events and filters.
表2列出了最有用的事件和过滤器。
Table 1 shows the events supported by an In-basket widget from the 4.5.2 release.
表1显示的是4.5.2发行版中In -basket小部件支持的事件。
Figure 12 shows the polling state of the adapter, polling for events from the event table (Figure 7b).
图12显示了从事件表中探测事件的适配器(图7 b)的探测状态。
Remember that the actionTransitionFunctions table is sparse; you defined functions for the events you expect in each state, and left all other cells empty.
请记住，actiontransitionfunctions表是稀疏的；为每个状态下期望出现的事件定义函数，其他单元格都空着。
The event table archive view (Figure 7a) contains information about the events that have been processed.
事件表档案文件视图(图7a)包含关于已经处理的事件的信息。
XPathHandler implements selected SAX events and issues the proper calls on the table class.
XPathHandler实现选中的SAX事件，并发出对表类的正确调用。
Table 1. Initial test environment: 1 GA, 1 MBean, 10 events per minute.
表1.初始测试环境：1个普通代理、1个Mbean、每分钟是10个事件。
应用推荐