We used a discussion database that supported seven views.
我们使用一个支持7个视图的讨论数据库。
Topic is a class that represents a topic in the Discussion database.
Topic是一个表示Discussion数据库中主题的类。
The discussion server could not connect to the discussion database.
讨论服务器无法连接到讨论储存处。
We may use this to display the categories in a discussion database as shown in figure 4.
我们使用它来显示讨论数据库中的类别，如图4所示。
The example used in this article is a set of Web services for the Discussion database template.
文中使用的示例是一组针对Discussion数据库模板的Web服务。
The Discussion database Web services are functionally decomposed into three different services.
Discussion数据库web服务在功能上可以分解为三种不同的服务。
Let's take for example a discussion database with 10,000 main topics and 100,000 response documents.
以一个讨论数据库为例，假设它有10,000个主题和100,000个响应文档。
The discussion database contains 113,000 documents and 23 categories and has full text index enabled.
讨论数据库包含 113,000篇文档和23 个类别，并支持全文索引。
The list methods provided by the Discussion database Web services return arrays of data transfer objects.
Discussion数据库web服务提供的列表方法返回数据传输对象数组。
Here's how: Suppose you have a discussion database with 10,000 main topics and 100,000 response documents.
方法如下：假设您有一个讨论数据库，其中包含10,000个主题和100,000个响应文档。
ntf from Lotus Domino 7.0, and the XPages discussion database was 700 MB with template discussion8.ntf
XPages讨论数据库，连同LotusDomino 8.5.2 的模板discussion8.ntf，大小是 700MB。
This section gives an overview of the architecture used in the Domino Discussion database Web services application.
本节将对DominoDiscussion数据库web服务应用程序中使用的架构进行概述。
For example, figure 4 shows a composite application with a discussion database Notes component view and a tag cloud.
例如，图4显示了一个复合应用程序，它带有一个讨论数据库Notes组件视图和一个标记云。
For example, the basic data element in a discussion database is an individual's contribution in the form of a document.
例如，讨论数据库中的基本数据元素是个人使用文档形式发表的帖子。
The classic discussion database showed fewer IOPs for the 200 users supported with response times less than one second.
经典讨论数据库显示，在支持200个用户且响应时间小于一秒的情况下，经典讨论数据库IOP更少。
Response is a class that represents a response to a topic or a response to another response in the Discussion database.
Response是一个表示Discussion数据库中主题的响应或响应的响应的类。
Additionally, categories can be selected in the tag cloud and that focus passed back to the discussion database component view.
此外，可以在标记云中选择类别，并将这个信息传回到讨论数据库组件视图中。
Figures 1-4 show the classic discussion database on Lotus Domino 8.5.2 and the XPages discussion database on the Lotus Domino 8.5.2.
图1 - 4显示了LotusDomino8.5.2上的经典讨论数据库，及Lotus Domino 8.5.2上的XPages讨论数据库。
The size of the discussion database increased because of the new features and the new discussion database template supported by XPages.
讨论数据库的大小也由于XPages支持的新特性和新讨论数据库模板而增加了。
For example, we created a query view based on the All Documents view in the discussion database. These are the fields that we wrote down.
例如，我们基于discussion数据库中的AllDocuments视图创建了一个查询视图。
Engineer a Web service layer on the Discussion database template to expose the key template functionality for consumption by a Web service client.
在 Discussion数据库模板上设计Web服务层以公开关键模板功能供 Web 服务客户机使用。
Figure 4 shows the classic discussion database and the XPages discussion database on Lotus Domino 8.5.2 with user response times of less than three seconds.
图4显示的是，用户响应时间小于三秒情况下，LotusDomino8.5.2上的经典讨论数据库和XPages讨论数据库。
The new and improved XPages discussion database on Lotus Domino 8.5.2 scaled to three times more concurrent users and total pages per second than the classic discussion database.
而LotusDomino8.5.2上的新改进的XPages讨论数据库的并发用户数和每秒总页数可比经典讨论数据库多三倍。
The goal of WS-I compliance is to guarantee the interoperability of the Discussion database Web services to allow their consumption by clients using other compliant Web service technologies.
WS-I依从性的目标是保证Discussion数据库Web服务之间的互操作性，允许客户机通过其他支持 Web服务的技术来使用这些服务。
The article also highlights some common tips in other areas, such as performance, without going into an extensive discussion of database analysis and design issues for these topic areas.
本文还列出了其他领域的一些常用技巧，比如性能，但是不会详细讨论这些主题领域的数据库分析和设计问题。
We conclude the discussion with a brief look at underlying and target 64-bit DB2 database instance setup and provide some best practices recommendations and performance enhancement tips.
在结束讨论前，我们将简要地看一看基本的64位DB 2目标数据库实例，并提供一些最佳实践建议和性能提高技巧。
The discussion focused on a couple of big issues of database design without getting into the details of query optimization and application considerations.
本文着重讨论了数据库设计的两个比较大的问题，而没有深入研究查询优化和应用程序考虑事项的细节。
The classic discussion application database scaled up to 200 concurrent users.
这个经典的讨论应用程序数据库可扩展至 200个并发用户。
While for the most part the discussion has been general, when it comes to actually loading the data into the database, the MassLoad program in WebSphere Commerce Loader package is used.
然而对于我们已经涵盖的大部分讨论而言，当它实际上加载数据到数据库中的时候，WebSphereCommerceloader包中的MassLoad程序是在被使用的。
The business logic of the database arranges these documents into discussion threads, with a child-parent hierarchal structure.
数据库的业务逻辑将通过child -parent层次结构把这些文档组织成讨论线索。
应用推荐