Skip to content

Commit 4a0d536

Browse files
authored
Update README.md
1 parent 0ea63ed commit 4a0d536

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

README.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
1-
# MongoDB Persistor
1+
# Vert.x 2.x is **deprecated** - use instead http://vertx.io/docs/vertx-mongo-client/java/
2+
3+
## MongoDB Persistor
24

35
This module allows data to be saved, retrieved, searched for, and deleted in a MongoDB instance. MongoDB is a great match
46
for persisting vert.x data since it natively handles JSON (BSON) documents.
57

6-
# WARNING - Vertx-3 now has new Mongo 'modules', this mod should only be used for vertx 2.x
7-
8-
####To use this module you must have a MongoDB instance running on your network.
8+
##### To use this module you must have a MongoDB instance running on your network.
99

1010
This is a multi-threaded worker module.
1111

12-
## Dependencies
12+
### Dependencies
1313

1414
This module requires a MongoDB server to be available on the network.
1515

16-
## Name
16+
### Name
1717

1818
The module name is `mongo-persistor`.
1919

20-
## Configuration
20+
### Configuration
2121

2222
The mongo-persistor module takes the following configuration:
2323

@@ -59,7 +59,7 @@ Let's take a look at each field in turn:
5959
* `read_preference` is the read preferences, see http://docs.mongodb.org/manual/core/read-preference/. Default is "primary".
6060
* `use_mongo_types` enable the use of mongo types such as Date, byte array, array list. Note that if enabled this will incur a performance overhead to all queries. Default is `false`.
6161

62-
### Replsets or sharding
62+
#### Replsets or sharding
6363

6464
If you want to use sharding or a replica set then you need to provide a list of seed addresses, these take
6565
priority over the host/port combination. For example:
@@ -76,11 +76,11 @@ priority over the host/port combination. For example:
7676

7777
The seeds variable takes a list of objects which specify the host and port of each member of your seed list.
7878

79-
## Operations
79+
### Operations
8080

8181
The module supports the following operations
8282

83-
### Save
83+
#### Save
8484

8585
Saves a document in the database.
8686

@@ -136,7 +136,7 @@ Where
136136
* `message` is an error message.
137137

138138

139-
### Update
139+
#### Update
140140

141141
Updates a document in the database.
142142
Uses the Mongodb update function: http://www.mongodb.org/display/DOCS/Updating
@@ -182,7 +182,7 @@ An example would be:
182182

183183

184184

185-
### Find
185+
#### Find
186186

187187
Finds matching documents in the database.
188188

@@ -282,7 +282,7 @@ Equivalence in mongoDB:
282282

283283
db.order.find().skip(10).limit(10)
284284

285-
#### Batching
285+
##### Batching
286286

287287
If a find returns many documents we do not want to load them all up into memory at once and send them in a single JSON message since this could result in the server running out of RAM.
288288

@@ -319,7 +319,7 @@ For instance, in JavaScript you might do something like:
319319
If there is more data to be requested and you do not reply to get the next batch within a timeout (see `timeout parameter`), then the underlying MongoDB cursor will be closed, and any further attempts to request more will fail.
320320

321321

322-
### Find One
322+
#### Find One
323323

324324
Finds a single matching document in the database.
325325

@@ -368,7 +368,7 @@ If an error occurs in finding the documents a reply is returned:
368368
Where
369369
*`message` is an error message.
370370

371-
### Find and modify
371+
#### Find and modify
372372

373373
The findAndModify command atomically modifies and returns a single document. By default, the returned document does not include the modifications made on the update. To return the document with the modifications made on the update, use the `new` option. See http://docs.mongodb.org/manual/reference/command/findAndModify/ for details:
374374

@@ -410,7 +410,7 @@ An example would be:
410410

411411
This would find a document in the `counters` collection with an `_id` of "people" and increment its `seq` field and reply successfully with the new document, as `new` was set to true.
412412

413-
### Count
413+
#### Count
414414

415415
Counts the number of documents within a collection:
416416

@@ -558,7 +558,7 @@ If an error occurs in finding the documents a reply is returned:
558558
Where
559559
*`message` is an error message.
560560

561-
### Get Collections List
561+
#### Get Collections List
562562

563563
Returns the list of collection names in the db:
564564

@@ -657,7 +657,7 @@ If an error occurs in finding the documents a reply is returned:
657657
Where
658658
* `message` is an error message.
659659

660-
### Drop Collection
660+
#### Drop Collection
661661

662662
Drops a collection from the db:
663663

@@ -699,7 +699,7 @@ Where
699699
* `message` is an error message.
700700

701701

702-
### Command
702+
#### Command
703703

704704
Runs an arbitrary MongoDB command.
705705

@@ -723,7 +723,7 @@ You would expect a result something like:
723723
"status":"ok"
724724
}
725725

726-
### writeConcern
726+
#### writeConcern
727727

728728
The operations save, update and delete have an optional field called "writeConcern". Setting this property in your request
729729
changes the "consistency" of that operation.

0 commit comments

Comments
 (0)