diff --git a/source/reference/method.txt b/source/reference/method.txt index 2f43ac8c27b..db270c152c9 100644 --- a/source/reference/method.txt +++ b/source/reference/method.txt @@ -429,10 +429,6 @@ Database - Removes the current database. - * - :method:`db.eval()` - - - Deprecated. Passes a JavaScript function for server-side JavaScript evaluation when run against MongoDB 4.0 or earlier. Unsupported when run against MongoDB 4.2 or later. - * - :method:`db.fsyncLock()` - Flushes writes to disk and locks the database to prevent write operations and assist backup operations. Wraps :dbcommand:`fsync`. @@ -473,10 +469,6 @@ Database - Returns the name of the current database. - * - :method:`db.getProfilingLevel()` - - - Returns the current profiling level for database operations. - * - :method:`db.getProfilingStatus()` - Returns a document that reflects the current profiling level and the profiling threshold. diff --git a/source/reference/method/db.eval.txt b/source/reference/method/db.eval.txt deleted file mode 100644 index 6efe2037121..00000000000 --- a/source/reference/method/db.eval.txt +++ /dev/null @@ -1,77 +0,0 @@ -========= -db.eval() -========= - -.. default-domain:: mongodb - -.. contents:: On this page - :local: - :backlinks: none - :depth: 1 - :class: singlecol - -Definition ----------- - -.. method:: db.eval(function, arguments) - - .. deprecated:: 3.0 - - .. important:: - - Starting in version 4.2, MongoDB removes the ``eval`` command. - The deprecated :method:`db.eval()`, which wraps the ``eval`` - command, can only be run against MongoDB 4.0 or earlier versions. - For behavior and example, refer to the 4.0 or earlier version of - the manual. - - Provides the ability to run JavaScript code on the MongoDB server. - - The method accepts the following parameters: - - - .. list-table:: - :header-rows: 1 - :widths: 20 20 80 - - * - Parameter - - - Type - - - Description - - * - ``function`` - - - function - - - A JavaScript function to execute. - - - - * - ``arguments`` - - - list - - - Optional. A list of arguments to pass to the JavaScript function. Omit if the function does not take arguments. - - - - - - The JavaScript function need not take any arguments, as in the first example, - or may optionally take arguments as in the second: - - .. code-block:: javascript - - function () { - // ... - } - - .. code-block:: javascript - - function (arg1, arg2) { - // ... - } - - - diff --git a/source/reference/method/db.getProfilingLevel.txt b/source/reference/method/db.getProfilingLevel.txt deleted file mode 100644 index 688c5ebb7e4..00000000000 --- a/source/reference/method/db.getProfilingLevel.txt +++ /dev/null @@ -1,20 +0,0 @@ -====================== -db.getProfilingLevel() -====================== - -.. default-domain:: mongodb - -.. contents:: On this page - :local: - :backlinks: none - :depth: 1 - :class: singlecol - -.. method:: db.getProfilingLevel() - - This method provides a wrapper around the database command - ":dbcommand:`profile`" and returns the current profiling level. - - .. deprecated:: 1.8.4 - - Use :method:`db.getProfilingStatus()` for related functionality. diff --git a/source/reference/method/js-database.txt b/source/reference/method/js-database.txt index e22189144dc..8b462d8caac 100644 --- a/source/reference/method/js-database.txt +++ b/source/reference/method/js-database.txt @@ -56,10 +56,6 @@ Database Methods - Removes the current database. - * - :method:`db.eval()` - - - Deprecated. Passes a JavaScript function for server-side JavaScript evaluation when run against MongoDB 4.0 or earlier. Unsupported when run against MongoDB 4.2 or later. - * - :method:`db.fsyncLock()` - Flushes writes to disk and locks the database to prevent write operations and assist backup operations. Wraps :dbcommand:`fsync`. @@ -100,10 +96,6 @@ Database Methods - Returns the name of the current database. - * - :method:`db.getProfilingLevel()` - - - Returns the current profiling level for database operations. - * - :method:`db.getProfilingStatus()` - Returns a document that reflects the current profiling level and the profiling threshold. @@ -223,7 +215,6 @@ Database Methods /reference/method/db.createView /reference/method/db.currentOp /reference/method/db.dropDatabase - /reference/method/db.eval /reference/method/db.fsyncLock /reference/method/db.fsyncUnlock /reference/method/db.getCollection @@ -234,7 +225,6 @@ Database Methods /reference/method/db.getLogComponents /reference/method/db.getMongo /reference/method/db.getName - /reference/method/db.getProfilingLevel /reference/method/db.getProfilingStatus /reference/method/db.getReplicationInfo /reference/method/db.getSiblingDB diff --git a/source/release-notes/1.8.txt b/source/release-notes/1.8.txt index 1871aaaa6c7..99f67488ced 100644 --- a/source/release-notes/1.8.txt +++ b/source/release-notes/1.8.txt @@ -342,7 +342,7 @@ Additional Changes and Enhancements - :update:`$rename` operator allows renaming of fields in a document. -- :method:`db.eval()` not to block. +- ``db.eval()`` not to block. - Geo queries with sharding. diff --git a/source/release-notes/3.0-compatibility.txt b/source/release-notes/3.0-compatibility.txt index 383bbe66386..3727521737b 100644 --- a/source/release-notes/3.0-compatibility.txt +++ b/source/release-notes/3.0-compatibility.txt @@ -543,13 +543,13 @@ The following commands and methods are deprecated in MongoDB 3.0: - :dbcommand:`diagLogging` -- ``eval``, :method:`db.eval()` +- ``eval``, ``db.eval()`` - :method:`db.collection.copyTo()` In addition, you cannot use the now deprecated ``eval`` -command or the :method:`db.eval()` method to invoke -:dbcommand:`mapReduce` or :method:`db.collection.mapReduce()`. +command or the ``db.eval()`` method to invoke :dbcommand:`mapReduce` or +:method:`db.collection.mapReduce()`. .. _3.0-date-timestamp: diff --git a/source/release-notes/3.0.txt b/source/release-notes/3.0.txt index 8a75f0d3efb..d4e34fdc9af 100644 --- a/source/release-notes/3.0.txt +++ b/source/release-notes/3.0.txt @@ -255,7 +255,7 @@ Issues fixed: Issues fixed: -- Deprecate :method:`db.eval()` and add warnings: +- Deprecate ``db.eval()`` and add warnings: :issue:`SERVER-17453` - Potential for abrupt termination with the Windows service stop diff --git a/source/release-notes/4.2-compatibility.txt b/source/release-notes/4.2-compatibility.txt index 05688a6bd0f..4c0684f4aa7 100644 --- a/source/release-notes/4.2-compatibility.txt +++ b/source/release-notes/4.2-compatibility.txt @@ -89,12 +89,12 @@ stage instead. Remove Support for the ``eval`` Command ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Starting in version 4.2, MongoDB removes the ``eval`` command. ``eval`` -command has been deprecated since version 3.0. +Starting in version 4.2, MongoDB removes the ``eval`` command. The +``eval`` command has been deprecated since version 3.0. The associated MongoDB 4.2 :binary:`~bin.mongo` shell methods -:method:`db.eval()` and :method:`db.collection.copyTo()` can only be -run when connected to MongoDB 4.0 or earlier. +``db.eval()`` and :method:`db.collection.copyTo()` can only be run when +connected to MongoDB 4.0 or earlier. .. _4.2-compat-remove-copydb-clone: diff --git a/source/release-notes/4.2.txt b/source/release-notes/4.2.txt index 256e29b4585..69ff99aaab1 100644 --- a/source/release-notes/4.2.txt +++ b/source/release-notes/4.2.txt @@ -483,9 +483,9 @@ Removed Commands and Methods - - - The MongoDB 4.2 :binary:`~bin.mongo` shell methods - :method:`db.eval()` and :method:`db.collection.copyTo()` can - only be run when connected to MongoDB 4.0 or earlier. + - The MongoDB 4.2 :binary:`~bin.mongo` shell methods ``db.eval()`` + and :method:`db.collection.copyTo()` can only be run when + connected to MongoDB 4.0 or earlier. * - ``copydb`` diff --git a/source/tutorial/manage-the-database-profiler.txt b/source/tutorial/manage-the-database-profiler.txt index ecc556ea959..0d7795ce41f 100644 --- a/source/tutorial/manage-the-database-profiler.txt +++ b/source/tutorial/manage-the-database-profiler.txt @@ -280,13 +280,6 @@ milliseconds, beyond which operations are considered *slow*. The ``sampleRate`` field indicates the percentage of *slow* operations that should be profiled. -To return only the profiling level, use the -:method:`db.getProfilingLevel()` helper in the :binary:`~bin.mongo` shell as in the following: - -.. code-block:: javascript - - db.getProfilingLevel() - Disable Profiling ~~~~~~~~~~~~~~~~~