买方应在发出采购订单表，由前60天交货时间。
Buyer shall issue the purchase order sheet by 60 days before the delivery time.
两列XML-typed列包含了订单表和整个表单。
The two XML-typed columns contain the orders table and the entire form.
对于订单表(参见清单2)，只需要将其绑定与一位客户和一个日期相关联，并允许折扣。
For the Order table (see Listing 2), you just want to tie it to a customer and a date and allow for a discount.
我们已经通过将采购订单文档存储为 BLOB，在基本关系数据库中尽量保持采购订单表模式简单。
We have tried to keep the purchase order table schema simple in the relational-only database by storing the purchase order document as a BLOB.
现在，我们开启会话2也更新订单表，不同的是更新的数据行为Id=2，同样的在数据行Id=2上也会申请排它锁至到更新事务的结束。
Now let's start session 2 and have it update another row in the Orders table. Same situation – session acquires and holds X lock on the row with (ID = 2).
下面的说明逐步地为该客户订单示例完成新的DB 2数据库以及必要的表和触发器的创建。
The following instructions walk through the creation of a new DB2 database along with the necessary tables and triggers for the Customer Order Example.
现在看一个常用的例子，即为国际订单设计词汇表。
Look at the common example of designing a vocabulary for international purchase orders.
对于一个事务，例如销售订单的创建，可能有十五个表，以及将要在每个表中进行比较的十到十五个之间的字段。
For a transaction such as the creation of a sales order, there may be fifteen tables and between ten and fifteen fields that are to be compared in each table.
清单1中的JDBC代码没有包含任何事务逻辑，它只是在数据库中保存TRADE表中的交易订单。
The JDBC code in Listing 1 includes no transaction logic, yet it persists the trade order in the TRADE table in the database.
该匿名块模拟为来自现有customer表的随机客户创建10个随机订单。
The anonymous block simulates the creation of 10 random orders for random customers from the existing customer table.
这个xsl样式表将按商品号对订单X ML进行排序，如清单2所示。
This XSL style sheet will sort the order XML by item number, as shown in Listing 2.
在表的末尾，添加一个包含订单的总成本的行。
At the end of the table, add a row containing the total cost of the order.
lineitem表，一个订单中的每样商品对应一行。
A LINEITEM table with one row for each item that is part of an order.
然后，从lineitem表中提取关于订单中尚未发货的各行项目的信息。
Information on individual line items that make up the orders, but are as yet unshipped, is then extracted from the LINEITEM table.
运行导入命令，用几个订单填充此表。
Run the import command to populate your table with a couple of orders.
运行了这些命令后，应该能够看到ACME .ORDERS表内的订单，如图1所示。
After you run these commands, you should be able to see orders in your ACME.ORDERS table as shown in figure 1.
然而，order表则具有该客户的所有订单，而不管订单的状态如何。
The order Table, however, has all the orders for the customer, no matter what the state of the order is.
在采购订单和产品表之间创建联接以获取产品详细信息。
Create a join between the purchase order and the product table to get product details.
如果在acme. orders表内没有任何订单，可以进行如下的操作。
If you don't have any orders in the acme.orders table, you can do the following.
OrderPriority作业首先提取'Building '市场客户的客户键，然后从ORDERS表中提取关于他们所下的订单的信息。
The OrderPriority job first extracts the customer keys for those customers who are in the 'Building' market segment, and then extracts information about orders placed by them from the orders table.
以上的fulfill_orders过程对orders表中未进行存货的每个订单调用order_items过程。
The fulfill_orders procedure above calls the order_items procedure for each order from the orders table that is not in backlog.
class标签把ORDER对象映射到ORDERS表，还有许多子标签用于描述其属性、ID订单名称，以及同models . Item的一对多关系。
The class tag maps the order object to the ORDERS table and has a number of sub tags that describe its properties, the ID and the order name, and a one-to-many relationship to models.Item.
通过运行和保存数据库表中的数据源内容，可以生成一个数据源来显示订单到达趋势。
By running and saving the feed content into a database table, you can generate a feed to show the order arrival trend.
但是该公司说，因为公交车是根据每个客户的订单单独设计的，它不能很容易地转换它的生产日程表，去填补延迟订单所产生的间歇。
But because its buses are engineered to order for each customer, the company said in a statement, it cannot easily switch its production schedule to fill the gaps left by the delayed order.
购买订单的一部分信息分解到关系副表中，用于建立间接索引。
Part of the purchase order information is shredded into relational side tables for indirect indexing.
一开始，从LINEITEM表中提取规定时期内通过邮寄或海运发货的行项目所对应的订单号。
Initially, order keys corresponding to line items shipped by mail or sea during the qualifying time period are extracted from the LINEITEM table.
因为采购订单不包含详细产品信息，所以需要进行单独查询，以便从产品表中查找产品详细信息。
Since the purchase order contains no detailed product information, a separate query is needed to find the product details from the product table.
考虑一个场景：一个顾客购物订单被存储在两个表中：ORDER和ORDER_ITEMS, ORDER中包含订购的总数，而ORDER_ITEMS中则包含订购的每一项商品的列表。
Consider a scenario where a customer purchase order is stored in two tables: order with the order summary and ORDER_ITEMS with the list of items for each order.
考虑一个场景：一个顾客购物订单被存储在两个表中：ORDER和ORDER_ITEMS, ORDER中包含订购的总数，而ORDER_ITEMS中则包含订购的每一项商品的列表。
Consider a scenario where a customer purchase order is stored in two tables: order with the order summary and ORDER_ITEMS with the list of items for each order.
应用推荐