我希望您在学习完本文后能够更好地理解某些xslt特性，并且能够编写更好的xslt样式表。
I hope that now you have better understanding of some XSLT features and that you will be able to write better XSLT stylesheets.
理解仓库目标表中的数据为何以及何时被意外地删除。
Understand why and when data in a warehouse target table was — accidentally — deleted.
您应当理解表空间、表和列的基本概念。
You should understand the basic concepts of tablespaces, tables, and columns.
如果在创建术语表结构之前详细回答这些问题，就能够构建一个便于用户理解并满足企业目标的结构。
If you answer these questions in detail before you create the glossary structure, you can build a structure that is simple for users to understand and that supports your enterprise goals.
要理解这种行为，需要知道运行了多少个select语句，以及需要读取表中的下一行数据的次数(而不是通过索引直接访问)。
To understand this behavior, you need to know how many SELECT statements were run and the number of times you had to read the next row in the table (rather than a direct access through an index).
既然您理解了维度和事实表的处理，就让我们看一看真实世界的例子，以探索如何从业务需求中识别维度和测度。
Now that you understand the process for both the dimension and fact tables, let's look at a real world example to explore how to identify the dimension and measures from the business requirements.
要理解词汇表类型之间的区别，一种方法是考虑不同的词汇表类型如何添加一个新的信息维度。
One way to understand the differences among the types of vocabulary is to think about adding a new dimension of information from one approach to the next.
当然可以采用文本格式列出此信息，但通过表更容易理解并方便进行更改。
While you can certainly list this information in a text format, the matrix makes the information easier to understand and to change.
如您所见，这个表更容易被业务用户理解、阅读和更新。
As you can see, this table is much easier to understood, read, and update by business users.
如果您熟悉表1中罗列的UML2的元素，那么理解那些部分应该不会有什么困难。
If you are familiar with the elements of UML 2 that are listed in Table 1, you should have no difficulty understanding those parts, either.
现在，您已经详细理解了前面几个迁移步骤，接下来我们执行剩下的迁移，以创建所需的其他表和关联。
Now that you understand the first few migration steps in detail, let's briefly go over the rest of the migrations to create the remaining tables and associations necessary.
就我们此处的目的而言，只要理解异步是通过优化器明智地放置TQ(表队列)操作符而引入到联邦查询计划之中的就足够了。
For our purposes, it suffices to understand that asynchrony is introduced into a federated query plan by the optimizer's judicious placement of the TQ (Table Queue) operator.
从模型入手可帮助您理解底层数据库表，之后再开始布设功能和UI。
Starting with the models can help you understand the underlying database tables before you begin layering on functionality and UI.
要理解此样式表，不妨先来看一下清单4 所示的输出。
To understand the stylesheet, it's easier to view the output as shown in Listing 4 first.
为了理解那些代码的意义，您需要获得存储在JLT_T077D和JLT _ TVT w表中的相应的人员可读性描述。
In order to understand the meaning of those codes you need to get the corresponding human readable descriptions that are stored in the JLT_T077D and JLT_TVTW tables.
为了让表或列的用途更容易理解，应当选择合适的名称。
To make it easier to understand the purpose of a table or a particular column, you should select appropriate names.
表4解释清单17中的代码段，帮助您更好地理解代码的作用及其实现方式。
Table 4 explains the code segment shown in Listing 17 to help you better understand what the code is trying to do, and how it goes about doing its job.
著名传播学学者麦克卢汉在其1964年发表的《理解媒介》一书中，用“媒介即讯息”来预言未来的摩登年代。
IN his 1964 book “Understanding Media, ” Marshall McLuhan helped define the modern age with his phrase, “The medium is the message.”
样式表作者常常错误地使用disable - out put -escaping (d - o - e)属性，没有充分理解标记和文本之间的区别。
The disable-output-escaping (d-o-e) attribute is often incorrectly used by 1.0 stylesheet writers without a full understanding of the distinction between markup and text.
为了理解本文附带的消息流和代码，表1对进入的消息的数据字段及其值进行了总结。
For reference purposes in understanding the attached message flow and code, Table 1 below summarises the inbound message data fields and their values.
至少，您应该理解如何安装和使用MySQL，以及如何在MySQL数据库中创建表。
At a minimum, you should understand how to set up and use MySQL and how to create tables in a MySQL database.
为了更好地理解不同配置和需求，表2列出了服务的内容。
To help better understand possible configurations and requirements, see Table 2, below, for how content should be served.
请保证在阅读本文之前，您已经熟悉了XSLT和XPath，且能理解HTML和XHTML的表结构。
Please make sure you are familiar with XSLT and XPath, and that you understand HTML and XHTML table structures before reading on.
连接器开发的第一步是理解存储库的词汇表、特性和布局，因此可行性研究就从这里开始。
The first step in connector development lies in understanding the vocabulary, features, and layout of your repository, so this is where the feasibility study begins.
这种两难境地归根结底为：模式必须在某种程度上符合开发人员和其他用户对词汇表的期望和理解。
The dilemma boils down to this: Up to a certain point, the schema must match the expectations and understanding of the developers and other users of the vocabulary.
很好地理解这一点对于改进您的样式表编码非常重要。
A good understanding of this is essential to improving your stylesheet coding.
尽管他缺乏强大的数学背景，但同事们表示，他对于资产负债表有着本能的理解。
While he lacks a strong background in mathematics, colleagues say he has an instinctive grasp of balance sheets.
在开始编程之前，我们首先需要理解构建日程表应用程序的一些规则，并弄清管理重复事件的过程。
Before we start programming, we need to first understand a few rules for building a calendar application and the process used in the management of recurring events.
专利案件在法官的日程表上可能被推迟几个月，甚至几年，而且其中通常包含法官不能理解的技术问题。
A patent case can tie up a judge's calendar for months, sometimes for years, and often involves technical issues that the judge doesn't understand.
我倾向于把这看作一则前言，或一则目录表，用来警醒读者们真正理解这一文本。
I would see it as a preface, or a table of contents, alerting the reader to what the book is about.
应用推荐