diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /lang/csharp/src/SecondaryDatabaseConfig.cs | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'lang/csharp/src/SecondaryDatabaseConfig.cs')
| -rw-r--r-- | lang/csharp/src/SecondaryDatabaseConfig.cs | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/lang/csharp/src/SecondaryDatabaseConfig.cs b/lang/csharp/src/SecondaryDatabaseConfig.cs index 1332b951..fc49a414 100644 --- a/lang/csharp/src/SecondaryDatabaseConfig.cs +++ b/lang/csharp/src/SecondaryDatabaseConfig.cs @@ -1,7 +1,7 @@ /*- * See the file LICENSE for redistribution information. * - * Copyright (c) 2009, 2012 Oracle and/or its affiliates. All rights reserved. + * Copyright (c) 2009, 2015 Oracle and/or its affiliates. All rights reserved. * */ using System; @@ -17,12 +17,12 @@ namespace BerkeleyDB { public class SecondaryDatabaseConfig : DatabaseConfig { private Database pdp; /// <summary> - /// All updates to Primary will be automatically reflected in the - /// secondary and all reads from the secondary will return corresponding + /// All updates to the primary database are automatically reflected in the + /// secondary and all reads from the secondary return corresponding /// data from Primary. /// </summary> /// <remarks> - /// Note that as primary keys must be unique for secondary indices to + /// As primary keys must be unique for secondary indices to /// work, Primary must have been configured with /// <see cref="DuplicatesPolicy.NONE"/>. /// </remarks> @@ -68,8 +68,8 @@ namespace BerkeleyDB { /// modify a primary database being used to populate a secondary /// database, in another thread of control, until /// <see cref="SecondaryDatabase.Open"/> has returned successfully in - /// the first thread. If transactions are being used, Berkeley DB will - /// perform appropriate locking and the application need not do any + /// the first thread. If transactions are being used, Berkeley DB + /// performs appropriate locking and the application need not do any /// special operation ordering. /// </para> /// </remarks> @@ -80,7 +80,7 @@ namespace BerkeleyDB { /// <remarks> /// <para> /// This setting can be used to optimize updates when the secondary key - /// in a primary record will never be changed after the primary record + /// in a primary record is never changed after the primary record /// is inserted. For immutable secondary keys, a best effort is made to /// avoid calling the secondary callback function when primary records /// are updated. This optimization may reduce the overhead of update |