clob
美 [klɒb] 
英 [klɒb]
英汉解释
例句
This article compares its performance with that of character large object (CLOB) and shredded XML storage.
本文比较了pureXML™技术与字符型大对象（CLOB）和分解式XML存储的性能。
This comparison is interesting because for a certain class of today's XML applications, CLOB columns are a commonly choice for XML storage.
这种比较是很有趣的，因为对于当今相当多的XML应用程序来说，CLOB列是XML存储最常用的选择。
I decided to use CLOBs (Character Large Objects) with a modern RDBMS to save these documents.
我决定使用新型RDBMS支持的CLOB（字符大对象，CharacterLargeObject）来保存这些XML文档。
Storing the PO as a CLOB allows you to use the DOM in the application code to retrieve the relevant information.
将PO存储为CLOB，则可以在应用程序代码中使用DOM来检索相关信息。
Since the RDBMS supported a Java API to insert and retrieve CLOBs, this was a very easy task.
因为RDBMS支持JavaAPI插入和检索CLOB，所以这是一项非常轻松的任务。
The parameter type used for XML documents in all the stored procedures is CLOB.
在所有存储过程中，用于XML文档的参数类型是CLOB。
Only a blind full document retrieval, which again ignores the internal XML structure, can quickly read XML documents from CLOB columns.
只有盲目、全面的文档检索（这会再次忽略内部XML结构）能够快速从CLOB列读取XML文档。
This overhead does not exist when reading full XML documents from a CLOB where the XML is already stored in text form.
当从CLOB（在CLOB中XML本来就是以文本形式存储的）读取完整的XML文档时，不存在此开销。
Selecting an XML column from a table also serializes its result into a CLOB.
从一个表中选择一个XML列也会导致结果被串行化为一个CLOB。
Inserting the same XML data into a CLOB column takes approximately half the time (53%).
向CLOB列插入相同的XML数据约占用一半的时间（53%）。
The CLOB data type is defined as a character large object capable of storing characters up to 2, 147, 483, 647 long.
CLOB数据类型定义为最多能够存储2,147,483,647个字符的字符大对象。
An easy way to identify this problem is to temporarily use CLOB types, which have no size restrictions, as target columns.
识别该问题的简易方法是临时使用CLOB类型作为目标列，它没有任何大小限制。
Notice that inserting data to an XML column is no different from inserting into any CLOB column.
注意插入数据到XML列中与插入数据到任何CLOB列中没有区别。
Note that XQUERY, by default, serializes its result set into a CLOB.
注意，默认情况下，XQUERY会将它的结果串行化为一个CLOB。
This is because CLOB inserts do not benefit as much from parallelism as XML column inserts.
这是因为CLOB插入从并行性中的获益不如XML列插入多。
Since logically the XML column appears the same as a VARCHAR, CLOB, or BLOB column, the INSERT statements are also similar.
因为从逻辑上看XML列与VARCHAR、CLOB或BLOB列相似，所以INSERT语句也是相似的。
Since CLOB inserts use direct writes, the file system cache is not needed and is pure overhead.
因为CLOB插入使用直接写入的方式，所以无需文件系统缓存，而仅有纯开销。
As expected, the elapsed insert time for both CLOB and XML columns is approximately linear in the number of documents inserted.
正如所料，CLOB和XML列占用的插入时间和插入的文档数成线性比例。
Another case is when you want to store a document in a database as a string or a Character Large Object (CLOB) without parsing it.
另外一种情况是，不用解析文档，而将其作为字符串或字符大对象（CharacterLargeObject，CLOB）存储在数据库中。
Many database systems allow you to store XML data as CLOBs or "shred" the data into relational tables.
许多数据库系统允许将XML数据存储为CLOB格式，或将数据“分解”到关系表中。
Gone are the days of storing XML data as a CLOB or shredding to relational tables.
将XML数据存储为CLOB或将其分割为关系表的时代已经过去。
There is a code page conversion to the SQL world if the value is serialized into a CHAR, VARCHAR, or CLOB type that is not FOR BIT DATA.
如果值被串行化为不是FORBITDATA的CHAR、VARCHAR或CLOB类型，那么会有一个到SQL世界的代码页转换。
The purchase order (PO) is stored as a CLOB in the relational database (as opposed to being shredded).
采购订单（PO）在关系数据库中存储为CLOB（而不分割）。
The other common technique is to simply dump your XML document inside a CLOB column in the database.
另一种常见的技术是直接把XML文档转储到数据库的CLOB列中。
Even if the Chinese or Russian documents were inserted as BLOBs, they cannot be serialized as CLOBs or CHAR-types without giving this error.
即使以BLOB形式插入中文或俄文文档，这些文档仍然不能串行化为CLOB或CHAR类型而不产生错误。
Smart large objects consist of character large object (CLOB) and binary large object (BLOB) data types.
智能大对象包括字符大对象（CLOB）和二进制大对象（BLOB）数据类型。
The above comparison shows the extreme impact of having a CLOB column, even a very short one.
前面的比较展示了使用CLOB列（虽然非常短）带来的巨大影响。
You can choose to make the underlying storage a CLOB column, a VARCHAR column, or files within the file system.
您可选择将CLOB列、VARCHAR列或文件系统内的文件用作基础存储。
Figure 3 shows that the increased workload intensity hurts CLOB performance drastically.
图3显示增加的工作负载密度大大影响了CLOB性能。
However, file system caching can help read operations on CLOB columns if no XML parsing is involved.
然而，如果不涉及XML解析，那么文件系统缓存能够帮助提高对CLOB列的读操作。
Prior to the DB2 9 release, XML data was either stored intact as a character large object (CLOB) or shredded to relational tables.
在DB29之前，XML数据要么作为字符大对象（CLOB）按原样存储，要么分解到关系表中。
A response message is returned as character LOB (CLOB) if issued by the server.
如果由服务器发出，则响应消息作为字符LOB（CLOB）返回。
Redirect the file into PDSQL using the operator, and pipe through a grep command, looking for CLOB fields.
利用重定向运算符将文件重新定位到PDSQL，并通过grep命令导入，查找CLOB域。
Side tables can avoid much of the XML parsing for CLOBs and can often make CLOB queries 100 times faster or more.
索引表能够避免许多针对CLOB的XML解析，这通常能够使CLOB查询速度快100倍或更多。
This means that XML is either stored in files, stored wholesale in database CLOBs, or shredded into distinct columns.
这意味着XML可以存储在文件中，或者大量存储在数据库CLOB中，或者解析为分离的列。
The system generates a list of all of the CLOB fields found in the defect table (see Table 2).
系统产生了所有CLOB字段的一个列表，这些字段列在defect表中（参见表2）。
It scales with the database, and XML-specific optimizations give it better performance than CLOBs.
它可随数据库进行扩展，并且特定于XML的优化使得它具有比CLOB更好的性能。
At present, stored procedures and user-defined functions do not have support for XML as a parameter, but they can easily be passed as CLOBs.
目前，存储过程和用户定义函数不支持XML作为参数，但是很容易作为CLOB传递XML。
Figure 5 shows the query performance (elapsed time) of all five test queries for both pureXML and CLOBs.
图5显示了对pureXML和CLOB进行的全部5个测试查询的查询性能（占用时间）。
The larger messages should be read or received as CLOB.
更大的消息应该以CLOB的形式读取或接收。
