• Download your favorite PSX Games • Extract Epsxe archive with Winrar • Extract your downloaded PSX games, if the file in ecm format. Epsxe 1.90 bios and plugins.

Note The following code snippets come from the example code that can be found with the driver source on github. Prerequisites • A running MongoDB on localhost using the default port for MongoDB 27017 • MongoDB Driver. See for instructions on how to install the MongoDB driver. Note If no top-level _id field is specified in the document, MongoDB automatically adds the _id field to the inserted document. Count Documents in A Collection To count the number of documents in a collection, you can use the collection’s method. The following code should print 101 (the 100 inserted via insertMany plus the 1 inserted via the insertOne). System.out.println(collection.count()); Query the Collection To query the collection, you can use the collection’s method.

Add an insert request to the bulk operation. Boolean, isOrdered(). Methods inherited from class java.lang.Object.

You can call the method without any arguments to query all documents in a collection or pass a filter to query for documents that match the filter criteria. The method returns a instance that provides a fluent interface for chaining other methods. Find the First Document in a Collection To return the first document in the collection, use the method without any parameters and chain to find() method the method.

If the collection is empty, the operation returns null.

My background is in Java where exceptions are time consuming and that's the main reason I'm asking - will the 'continueOnError' option be time consuming??? The ContinueOnError flag for only affects the behaviour of the batch processing: rather than stopping processing on the first error encountered, the full batch will be processed. In MongoDB 2.4 you will only get a single error for the batch, which will be the last error encountered. This means if you do care about catching errors you would be better doing individual inserts. The main time savings for bulk insert vs single insert is reduced network round trips. Instead of sending a message to the MongoDB server per document inserted, drivers can break down bulk inserts into batches of up to the accepted by the mongod server (currently 48Mb). Are bulk inserts appropriate for this use case?

Given your use case of only 100s (or even 1000s) of documents to insert where 80% already exist, there may not be a huge benefit in using bulk inserts (especially if this process only happens every few days). Your small inserts will be combined in batches, but 80% of the documents don't actually need to be sent to the server. I would still favour bulk insert with ContinueOnError over your approach of deletion and re-insertion, but bulk inserts may be an unnecessary early optimisation given the number of documents you are wrangling and the percentage that actually need to be inserted. I would suggest doing a few runs with the different approaches to see what the actual impact is for your use case. MongoDB 2.6 As a head's up, the batch functionality is being significantly improved in the MongoDB 2.5 development series (which will culminate in the 2.6 production release). Free brochure templates for students. Planned features include support for bulk upserts and accumulating per-document errors rather than a single error per batch. The new write commands will require driver changes to support, but may change some of the assumptions above.