@@ -38,7 +38,9 @@ you can use regular expressions:
38
38
39
39
The regular expression pattern you pass into a filter must follow the :query:`regex <$regex>` syntax supported by the MongoDB server.
40
40
41
- Regular expressions in filter documents use the following ``options``:
41
+ Regular expressions in filter documents use ``options`` listed in the :query:`regex
42
+ <$regex>` guide. ``options`` is a string of concatenated options. For example, to specify
43
+ the ``i`` and ``s`` options, pass in "si" to ``options``.
42
44
43
45
.. list-table::
44
46
:header-rows: 1
@@ -141,8 +143,8 @@ creating a series of filters for individual databases or groups of collections.
141
143
Details
142
144
=======
143
145
144
- Regular Expression Options
145
- --------------------------
146
+ Regular Expression Options Example
147
+ ----------------------------------
146
148
147
149
``databaseRegex`` and ``collectionsRegex`` each supports an ``options`` field,
148
150
which you can use to configure regular expression options.
@@ -151,7 +153,10 @@ Internally, ``mongosync`` passes the filter and options to the
151
153
with Filtred Sync.
152
154
153
155
For example, this filter would match collections in the ``sales`` database
154
- that begin start with the ``accounts_`` string:
156
+ that begin with the ``accounts_`` string. The filter also specifies the option ``m`` to
157
+ match characters at the beginning or end of each line for strings with multiline values, and the
158
+ option ``s`` to allow the dot character to match all characters including newline
159
+ characters.
155
160
156
161
.. code-block:: json
157
162
0 commit comments