修改了 message system

This commit is contained in:
2023-07-04 14:10:13 +08:00
parent a764f9fcab
commit 5b12450a56
53 changed files with 603 additions and 281 deletions

View File

@@ -161,12 +161,12 @@ class MONGOCXX_API create_collection_deprecated {
const stdx::optional<std::int64_t>& size() const;
///
/// Specify configuration to the message_base on a per-collection basis.
/// Specify configuration to the storage on a per-collection basis.
///
/// @note This option is currently only available with the WiredTiger message_base engine.
/// @note This option is currently only available with the WiredTiger storage engine.
///
/// @param storage_engine_opts
/// Configuration options specific to the message_base engine.
/// Configuration options specific to the storage engine.
///
/// @return
/// A reference to the object on which this member function is being called. This facilitates
@@ -176,10 +176,10 @@ class MONGOCXX_API create_collection_deprecated {
bsoncxx::document::view_or_value storage_engine_opts);
///
/// Gets the current message_base engine configuration for this collection.
/// Gets the current storage engine configuration for this collection.
///
/// @return
/// Configuration options specific to the message_base engine.
/// Configuration options specific to the storage engine.
///
const stdx::optional<bsoncxx::document::view_or_value>& storage_engine() const;

View File

@@ -41,7 +41,7 @@ namespace options {
class MONGOCXX_API index {
public:
///
/// Base class representing the optional message_base engine options for indexes.
/// Base class representing the optional storage engine options for indexes.
///
class MONGOCXX_API base_storage_options {
public:
@@ -53,7 +53,7 @@ class MONGOCXX_API index {
};
///
/// Class representing the optional WiredTiger message_base engine options for indexes.
/// Class representing the optional WiredTiger storage engine options for indexes.
///
class MONGOCXX_API wiredtiger_storage_options final : public base_storage_options {
public:
@@ -216,11 +216,11 @@ class MONGOCXX_API index {
const stdx::optional<bool>& sparse() const;
///
/// Optionally used only in MongoDB 3.0.0 and higher. Specifies the message_base engine options for
/// Optionally used only in MongoDB 3.0.0 and higher. Specifies the storage engine options for
/// the index.
///
/// @param storage_options
/// The message_base engine options for the index.
/// The storage engine options for the index.
///
/// @return
/// A reference to the object on which this member function is being called. This facilitates
@@ -229,11 +229,11 @@ class MONGOCXX_API index {
index& storage_options(std::unique_ptr<base_storage_options> storage_options);
///
/// Optionally used only in MongoDB 3.0.0 and higher. Specifies the WiredTiger-specific message_base
/// Optionally used only in MongoDB 3.0.0 and higher. Specifies the WiredTiger-specific storage
/// engine options for the index.
///
/// @param storage_options
/// The message_base engine options for the index.
/// The storage engine options for the index.
///
index& storage_options(std::unique_ptr<wiredtiger_storage_options> storage_options);

View File

@@ -37,7 +37,7 @@ class uri;
/// collection level. The read concern can also be provided via connection string, and will be
/// parsed and set on the client constructed for the URI.
///
/// For the WiredTiger message_base engine, MongoDB 3.2 introduced the readConcern option for replica
/// For the WiredTiger storage engine, MongoDB 3.2 introduced the readConcern option for replica
/// sets and replica set shards. The readConcern option allows clients to choose a level of
/// isolation for their reads. You can specify a readConcern of "majority" to read data that has
/// been written to a majority of nodes and thus cannot be rolled back. By default, MongoDB uses a
@@ -45,7 +45,7 @@ class uri;
///
/// MongoDB 3.4 introduces a read concern level of "linearizable" to read data that has been written
/// to a majority of nodes (i.e. cannot be rolled back) @b and is not stale. Linearizable read
/// concern is available for all MongoDB supported message_base engines and applies to read operations on
/// concern is available for all MongoDB supported storage engines and applies to read operations on
/// a single document. Note that writes must be made with majority write concern in order for reads
/// to be linearizable.
///