| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
Remove leading comments that are just stating the filename.
Move any file-level comments below the copyright banner.
Remove leading blank lines.
|
| | |
|
| |
|
|
| |
prior to being interpreted as a long long
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are numerous places in the codebase where `mongo::Status` or
`mongo::StatusWith< T >` objects are returned and never checked.
Many of these are innocuous, but many of them are potentially
severe bugs. This change introduces facilities to permit
compile-time warning of unchecked `Status` and `StatusWith` usage
on clang compilers. It introduces an `ignore` function which is
useful to state that a specific "ignored status" case was
intentional. It not presently an error, in clang builds, to
forget to check a `Status` -- this will come in a later commit.
This also introduces a `transitional_ignore` function, which allows
for easy continual auditing of the codebase for current "whitelisted"
unchecked-status instances. All present "ignored status" cases
have been marked `transitional_ignore`.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
It is possible for older versions of MongoDB to save invalid collection
options which should be ignored. Older versions also would include a
'create' field in the collection options when a collection was created,
and possibly re-order the fields of the options document during a
subsequent 'collMod'. If the 'create' option is present at all, we
should take that to mean that these options were created on an older
version of MongoDB, and ignore unknown options. Otherwise, we should
reject unknown options.
(cherry picked from commit 6fba074768fad5f47611de38682257257005a1a6)
|
| | |
|
| |
|
|
|
| |
This ensures that we can handle collection metadata created
on version 2.4 or earlier.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
BSONObj instances should now be compared via the comparator
interface's evaluate() method. This preferred over using
BSONObj::woCompare() directly. If the comparison doesn't
require any database semantics (e.g. there is no collation),
there is a global instance of the SimpleBSONObjComparator
which should be used for BSONObj comparisons. If the
comparison requires special semantics, then callers must
instantiate their own comparator object.
|
| |
|
|
|
|
|
|
| |
Adds the basic infrastructure for read-only non-materialized views, as well as
the ability to create them (but not use them).
Views are disabled by default unless mongod is given the setParameter
enableViews=1.
|
| | |
|
| |
|
|
|
|
|
|
| |
default
Also ensures that the full BSON representation of the
collation spec associated with an index or with a collection
is materialized in the catalog.
|
| |
|
|
|
| |
The collator is parsed from BSON provided by the
CollectionCatalogEntry's CollectionOptions.
|
| | |
|
| |
|
|
|
| |
This covers setting and changing the validator as well as enforcing it for
insert and update.
|
| |
|
|
| |
CollectionOptions::validate()
|
| | |
|
| |
|
|
|
|
| |
index options"
This reverts commit aa207c8f93ca264fd292980defca1cff315f2a47.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
