Using lookup tables to add metadata
使用查询表添加元数据
C: Gperf generates lookup tables as discussed earlier.
C：前面讨论了Gperf将生成查找表。
This attribute is useful for small lookup tables.
这个属性对小的查找表有用。
Maybe you want to synchronize local lookup tables from a common source.
或者需要同步来自公共源的本地查找表。
Database partition 0 is typically used for storing small, non-partitioned lookup tables.
数据库分区0通常用于存储小型的非分区的查找表。
Probably the simplest useful code generator you could write would be one to build static lookup tables.
可以编写的最简单的可用代码生成器也许就是构建一个静态查找表。
The solution is to ignore complexities like lookup tables or expecting the memcached server to handle the process for you.
问题的解决方案就是忽略复杂的东西，比如查找表，或是寄望memcached服务器来为您处理这个过程。
The PI control and fuzzy control were used to design engine fuzzy PI throttle controller and lookup tables were given.
应用模糊控制方法建立了油门的模糊pi控制系统，给出了参数查询表。
This was necessary for fields where lookup tables were established in DB2 to hold the limited set of values for that field.
如果在DB 2中建立了查找表来保存字段的值的有限集，那么这对于该字段是必需的。
The -c option creates the lookup tables declared with the const keyword; the contents of all generated lookup tables then are constant-that is, read-only.
c选项将创建使用const关键字声明的查找表。所有生成的查找表中的内容都是常量—即只读形式。
It is rare in an OLTP query for the lookup tables to be selected as the primary query tables requiring an index on the dependent table to support the join.
OLTP查询中很少需要选择查找表作为需要相关表上的索引来支持联接的主查询表。
Listing 1 is the example implementation (from the most recent tip) of lookup tables that can provide a default value when the item being looked up is not found.
清单1是查找表的示例实现(摘自最近的那篇技巧)，在查找失败时，它可以提供默认值。
When lookup tables are used in joins with other large partitioned table spaces, you can maximize the parallelism in the join by partitioning the lookup tables as well.
当将查找（lookup）表与其他较大的分区的表相连接时，通过将查找表也进行分区，可以最大化并行度。
In addition to using lookup tables to extract additional metadata, other techniques can be used to make the form consistent with other user interface development standards.
除了使用查询表提取额外元数据之外，还可以使用其他技术让表单与其他用户界面开发标准保持一致。
This is a major advantage for lookup tables: since there are no conditions to evaluate, there is little or no additional overhead as the number of possible values increases.
使用查表法的一个主要优点是：由于没有条件判断，当候选值数量增加时，很少，甚至没有增加额外的性能开销。
With side tables, DB2 first performs an index lookup on the side table and then joins the corresponding row with the main table that contains the CLOBs.
在使用索引表的情况下，DB 2首先对索引表执行索引查找，然后将对应的行和包含CLOB的主表相结合。
The resulting code for handling all aspects of this lookup was straightforward but rather unwieldy, especially if you happen to have multiple tables that you want to use throughout a transform.
处理这类查找的代码非常简单但是相当笨拙，尤其是在转换中使用多个表的时候。
The transformer carries out a lookup action in non-primary tables for records of the primary table.
对于主表的记录，转换器对非主表进行查找。
You define your database format with three tables, and proceed to query them, showing that you can both emulate traditional SQL SELECT, and also provide an associative lookup.
定义一个具有3个表的数据库，然后对它们进行查询，既可以模仿传统的SQLSELECT，也可以进行关联查找。
An alternative approach is to use a lookup table strategy that relies on code tables.
另一种方法是使用查询表策略，这依赖于编码表。
The game workload is much more like Lightweight Directory Access Protocol (LDAP) or telephony directory lookup: lots and lots of small transactions over simple tables.
游戏的负载更接近于 LightweightDirectoryAccessProtocol（LDAP）或电话簿查询：对简单的表执行大量的小事务。
A lookup on tables, based on the schema.
一个基于模式的表查找。
From the new tables, the query inherits Lookup fields, which let you change field values by picking values from a list instead of having to correctly type a value.
从新表中，查询继承了“查阅”字段，这样您就可以从列表中挑选值来更改字段的值，而不必正确地键入值。
From the new tables, the query inherits Lookup fields, which let you change field values by picking values from a list instead of having to correctly type a value.
从新表中，查询继承了“查阅”字段，这样您就可以从列表中挑选值来更改字段的值，而不必正确地键入值。
应用推荐