.. _motor-tutorial: Motor 指南 ============== .. These setups are redundant because I can't figure out how to make doctest run a common setup *before* the setup for the two groups. A "testsetup:: *" is the obvious answer, but it's run *after* group-specific setup. .. testsetup:: before-inserting-2000-docs import pymongo import motor import tornado.web from tornado.ioloop import IOLoop from tornado import gen db = motor.MotorClient().open_sync().test_database .. testsetup:: after-inserting-2000-docs import pymongo import motor import tornado.web from tornado.ioloop import IOLoop from tornado import gen db = motor.MotorClient().open_sync().test_database pymongo.MongoClient().test_database.test_collection.insert( [{'i': i} for i in range(2000)]) .. testcleanup:: * import pymongo pymongo.MongoClient().test_database.test_collection.remove() A guide to using *MongoDB* and *Tornado* with *Motor*, the non-blocking driver. Tutorial Prerequisites -------------------- 在你学习Motor之前, 你可以通过 `MongoDB 指南`_ 学习MongoDB. 安装 pip_ 然后执行: $ pip install motor 安装后, 在Python shell中执行如下命令将不会导致异常: .. doctest:: >>> import motor 这个指南假设在默认的host(主机)和port(端口)上已经运行着一个MongoDB实例. 假设你已经`下载并安装 `_ MongoDB, 你可以这样运行它: .. code-block:: bash $ mongod .. _pip: http://www.pip-installer.org/en/latest/installing.html .. _MongoDB 指南: http://docs.mongodb.org/manual/tutorial/getting-started/ 对象层次 ---------------- Motor, 就像PyMongo, 以4级的对象层次来表现数据: * :class:`~motor.MotorClient` / :class:`~motor.MotorReplicaSetClient`: 代表一个mongod进程, 或者它们的一个集群. 你明确的创建一个客户端对象, 然后将它连接到一个运行着的mongod或mongods, 然后在你应用程序的生命周期中使用它. * :class:`~motor.MotorDatabase`: 每个mongod有一组数据库(与磁盘上的一组数据文件不同). 你可以通过客户端(client)获得一个数据库的引用. * :class:`~motor.MotorCollection`: 每个数据库中有一组集合(collections), 集合中包含文档(documents); 你可以通过数据库获得集合的一个引用. * :class:`~motor.MotorCursor`: 在 :class:`~motor.MotorCollection` 上执行 :meth:`~motor.MotorCollection.find` 获得一个 :class:`~motor.MotorCursor` 对象, 代表了符合查询条件(query)的一组文档(documents). 创建一个客户端(Client) ----------------- 在你应用程序启动时, 你创建 :class:`~motor.MotorClient` 或 :class:`~motor.MotorReplicaSetClient` 的一个实例. (查看 `high availability and PyMongo`_ for an introduction to MongoDB replica sets and how PyMongo connects to them.) 在执行任何操作之前, 你必须在客户端对象上调用 :meth:`~motor.MotorClient.open_sync` : .. doctest:: before-inserting-2000-docs >>> client = motor.MotorClient().open_sync() 这个操作连接至 ``mongod`` 并监听默认的host(主机)和port(端口). 你能像下面这样指定host(主机)和port(端口): .. doctest:: before-inserting-2000-docs >>> client = motor.MotorClient('localhost', 27017).open_sync() Motor 同样支持 `connection URIs`_:: >>> client = motor.MotorClient('mongodb://localhost:27017').open_sync() .. _high availability and PyMongo: http://api.mongodb.org/python/current/examples/high_availability.html .. _connection URIs: http://docs.mongodb.org/manual/reference/connection-string/ 获得一个数据库 ------------------ 一个单独的MongoDB实例能支持多个独立的`databases `_. 从一个打开的客户端, 你能获得一个指定数据库的引用, 使用点号表达式或者中括号表达式: .. doctest:: before-inserting-2000-docs >>> db = client.test_database >>> db = client['test_database'] 创建一个对数据库的引用并没有I/O操作也不接收回调函数(callback)或返回一个Future. Tornado 应用程序启动序列 ------------------------------------ 现在我们可以创建一个客户端并获得一个数据库, 我们已经准备好了开发一个使用Motor的Tornado应用程序. :meth:`~motor.MotorClient.open_sync` 是一个阻塞操作, 所以它必须在监听HTTP请求之前被调用. 这里是一个Tornado web应用程序启动序列的示例:: db = motor.MotorClient().open_sync().test_database application = tornado.web.Application([ (r'/', MainHandler) ], db=db) application.listen(8888) tornado.ioloop.IOLoop.instance().start() Passing the database as the ``db`` keyword argument to ``Application`` makes it available to request handlers:: class MainHandler(tornado.web.RequestHandler): def get(self): db = self.settings['db'] If you want to use the Tornado HTTP server's `start() method`_ to fork multiple subprocesses, you must create the client object **after** calling ``start()``, since a client created before forking isn't valid after:: application = tornado.web.Application([ (r'/', MainHandler) ]) server = tornado.httpserver.HTTPServer(application) server.bind(8888) # start(0) starts a subprocess for each CPU core server.start(0) db = motor.MotorClient().open_sync().test_database # Delayed initialization of settings application.settings['db'] = db tornado.ioloop.IOLoop.instance().start() .. warning:: It is a common mistake to create a new client object for every request; this comes at a dire performance cost. Create the client when your application starts and reuse that one client for the lifetime of the process, as shown in these examples. .. _start() method: http://tornadoweb.org/en/stable/netutil.html#tornado.netutil.TCPServer.start 获得一个集合 -------------------- A `collection `_ is a group of documents stored in MongoDB, and can be thought of as roughly the equivalent of a table in a relational database. Getting a collection in Motor works the same as getting a database: .. doctest:: before-inserting-2000-docs >>> collection = db.test_collection >>> collection = db['test_collection'] Just like getting a reference to a database, getting a reference to a collection does no I/O and doesn't accept a callback or return a Future. 插入一个文档 -------------------- 和PyMongo一样, Motor使用Python的字典来代表MongoDB的文档. 要在MongoDB中存储一个文档, 调用 :meth:`~motor.MotorCollection.insert` , 参数为一个文档和一个回调函数: .. doctest:: before-inserting-2000-docs >>> from tornado.ioloop import IOLoop >>> def my_callback(result, error): ... print 'result', repr(result) ... IOLoop.instance().stop() ... >>> document = {'key': 'value'} >>> db.test_collection.insert(document, callback=my_callback) >>> IOLoop.instance().start() result ObjectId('...') There are several differences to note between Motor and PyMongo. One is that, unlike PyMongo's :meth:`~pymongo.collection.Collection.insert`, Motor's has no return value. Another is that ``insert`` accepts an optional callback function. The function must take two arguments and it must be passed to ``insert`` as a keyword argument, like:: db.test_collection.insert(document, callback=some_function) .. warning:: Passing the callback function using the ``callback=`` syntax is required. (This requirement is a side-effect of the technique Motor uses to wrap PyMongo.) If you pass the callback as a positional argument instead, you may see an exception like ``TypeError: method takes exactly 1 argument (2 given)``, or ``TypeError: callable is required``, or some silent misbehavior. :meth:`insert` is *asynchronous*. This means it returns immediately, and the actual work of inserting the document into the collection is performed in the background. When it completes, the callback is executed. If the insert succeeded, the ``result`` parameter is the new document's unique id and the ``error`` parameter is ``None``. If there was an error, ``result`` is ``None`` and ``error`` is an ``Exception`` object. For example, we can trigger a duplicate-key error by trying to insert two documents with the same unique id: .. doctest:: before-inserting-2000-docs >>> ncalls = 0 >>> def my_callback(result, error): ... global ncalls ... print 'result', repr(result), 'error', repr(error) ... ncalls += 1 ... if ncalls == 2: ... IOLoop.instance().stop() ... >>> document = {'_id': 1} >>> db.test_collection.insert(document, callback=my_callback) >>> db.test_collection.insert(document, callback=my_callback) >>> IOLoop.instance().start() result 1 error None result None error DuplicateKeyError(u'E11000 duplicate key error index: test_database.test_collection.$_id_ dup key: { : 1 }',) The first insert results in ``my_callback`` being called with result 1 and error ``None``. The second insert triggers ``my_callback`` with result None and a :class:`~pymongo.errors.DuplicateKeyError`. A typical beginner's mistake with Motor is to insert documents in a loop, not waiting for each insert to complete before beginning the next:: >>> for i in range(2000): ... db.test_collection.insert({'i': i}) .. Note that the above is NOT a doctest!! In PyMongo this would insert each document in turn using a single socket, but Motor attempts to run all the :meth:`insert` operations at once. This requires up to ``max_concurrent`` [#max_concurrent]_ open sockets connected to MongoDB, which taxes the client and server. To ensure instead that all inserts use a single connection, wait for acknowledgment of each. This is a bit complex using callbacks: .. doctest:: before-inserting-2000-docs >>> i = 0 >>> def do_insert(result, error): ... global i ... if error: ... raise error ... i += 1 ... if i < 2000: ... db.test_collection.insert({'i': i}, callback=do_insert) ... else: ... IOLoop.instance().stop() ... >>> # Start >>> db.test_collection.insert({'i': i}, callback=do_insert) >>> IOLoop.instance().start() You can simplify this code with ``gen.coroutine``. Using Motor with `gen.coroutine` -------------------------------- The `tornado.gen module`_ lets you use generators to simplify asynchronous code. There are two parts to coding with ``gen``: ``gen.coroutine`` and ``Future``. First, decorate your generator function with ``@gen.coroutine``: >>> @gen.coroutine ... def do_insert(): ... pass If you pass no callback to one of Motor's asynchronous methods, it returns a ``Future``. Yield the ``Future`` instance to wait for an operation to complete and obtain its result: .. doctest:: before-inserting-2000-docs >>> @gen.coroutine ... def do_insert(): ... for i in range(2000): ... future = db.test_collection.insert({'i': i}) ... result = yield future ... >>> IOLoop.current().run_sync(do_insert) In the code above, ``result`` is the ``_id`` of each inserted document. .. seealso:: `Bulk inserts in PyMongo `_ .. seealso:: :ref:`Detailed example of Motor and gen.coroutine ` .. _tornado.gen module: http://tornadoweb.org/en/stable/gen.html .. mongodoc:: insert Getting a Single Document With :meth:`~motor.MotorCollection.find_one` ---------------------------------------------------------------------- Use :meth:`~motor.MotorCollection.find_one` to get the first document that matches a query. For example, to get a document where the value for key "i" is less than 2: .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_find_one(): ... document = yield db.test_collection.find_one({'i': {'$lt': 2}}) ... print document ... >>> IOLoop.current().run_sync(do_find_one) {u'i': 0, u'_id': ObjectId('...')} The result is a dictionary matching the one that we inserted previously. .. note:: The returned document contains an ``"_id"``, which was automatically added on insert. .. mongodoc:: find Querying for More Than One Document ----------------------------------- Use :meth:`~motor.MotorCollection.find` to query for a set of documents. :meth:`~motor.MotorCollection.find` does no I/O and does not take a callback, it merely creates a :class:`~motor.MotorCursor` instance. The query is actually executed on the server when you call :meth:`~motor.MotorCursor.to_list` or :meth:`~motor.MotorCursor.each`, or yield :attr:`~motor.MotorCursor.fetch_next`. To find all documents with "i" less than 5: .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_find(): ... cursor = db.test_collection.find({'i': {'$lt': 5}}) ... for document in (yield cursor.to_list(length=100)): ... print document ... >>> IOLoop.current().run_sync(do_find) {u'i': 0, u'_id': ObjectId('...')} {u'i': 1, u'_id': ObjectId('...')} {u'i': 2, u'_id': ObjectId('...')} {u'i': 3, u'_id': ObjectId('...')} {u'i': 4, u'_id': ObjectId('...')} A ``length`` argument is required when you call to_list to prevent Motor from buffering an unlimited number of documents. To get one document at a time with :attr:`~motor.MotorCursor.fetch_next` and :meth:`~motor.MotorCursor.next_object`: .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_find(): ... cursor = db.test_collection.find({'i': {'$lt': 5}}) ... while (yield cursor.fetch_next): ... document = cursor.next_object() ... print document ... >>> IOLoop.current().run_sync(do_find) {u'i': 0, u'_id': ObjectId('...')} {u'i': 1, u'_id': ObjectId('...')} {u'i': 2, u'_id': ObjectId('...')} {u'i': 3, u'_id': ObjectId('...')} {u'i': 4, u'_id': ObjectId('...')} You can apply a sort, limit, or skip to a query before you begin iterating: .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_find(): ... cursor = db.test_collection.find({'i': {'$lt': 5}}) ... # Modify the query before iterating ... cursor.sort([('i', pymongo.DESCENDING)]).limit(2).skip(2) ... while (yield cursor.fetch_next): ... document = cursor.next_object() ... print document ... >>> IOLoop.current().run_sync(do_find) {u'i': 2, u'_id': ObjectId('...')} {u'i': 1, u'_id': ObjectId('...')} ``fetch_next`` does not actually retrieve each document from the server individually; it gets documents efficiently in `large batches`_. .. _`large batches`: http://docs.mongodb.org/manual/core/read-operations/#cursor-behaviors Counting Documents ------------------ Use :meth:`~motor.MotorCursor.count` to determine the number of documents in a collection, or the number of documents that match a query: .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_count(): ... n = yield db.test_collection.find().count() ... print n, 'documents in collection' ... n = yield db.test_collection.find({'i': {'$gt': 1000}}).count() ... print n, 'documents where i > 1000' ... >>> IOLoop.current().run_sync(do_count) 2000 documents in collection 999 documents where i > 1000 :meth:`~motor.MotorCursor.count` uses the *count command* internally; we'll cover commands_ below. .. seealso:: `Count command `_ Updating Documents ------------------ :meth:`~motor.MotorCollection.update` changes documents. It requires two parameters: a *query* that specifies which documents to update, and an update document. The query follows the same syntax as for :meth:`find` or :meth:`find_one`. The update document has two modes: it can replace the whole document, or it can update some fields of a document. To replace a document: .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_replace(): ... coll = db.test_collection ... old_document = yield coll.find_one({'i': 50}) ... print 'found document:', old_document ... _id = old_document['_id'] ... result = yield coll.update({'_id': _id}, {'key': 'value'}) ... print 'replaced', result['n'], 'document' ... new_document = yield coll.find_one({'_id': _id}) ... print 'document is now', new_document ... >>> IOLoop.current().run_sync(do_replace) found document: {u'i': 50, u'_id': ObjectId('...')} replaced 1 document document is now {u'_id': ObjectId('...'), u'key': u'value'} You can see that :meth:`update` replaced everything in the old document except its ``_id`` with the new document. Use MongoDB's modifier operators to update part of a document and leave the rest intact. We'll find the document whose "i" is 51 and use the ``$set`` operator to set "key" to "value": .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_update(): ... coll = db.test_collection ... result = yield coll.update({'i': 51}, {'$set': {'key': 'value'}}) ... print 'updated', result['n'], 'document' ... new_document = yield coll.find_one({'i': 51}) ... print 'document is now', new_document ... >>> IOLoop.current().run_sync(do_update) updated 1 document document is now {u'i': 51, u'_id': ObjectId('...'), u'key': u'value'} "key" is set to "value" and "i" is still 51. By default :meth:`update` only affects the first document it finds, you can update all of them with the ``multi`` flag:: yield coll.update({'i': {'$gt': 100}}, {'$set': {'key': 'value'}}, multi=True) .. mongodoc:: update Saving Documents ---------------- :meth:`~motor.MotorCollection.save` is a convenience method provided to insert a new document or update an existing one. If the dict passed to :meth:`save` has an ``"_id"`` key then Motor performs an :meth:`update` (upsert) operation and any existing document with that ``"_id"`` is overwritten. Otherwise Motor performs an :meth:`insert`. .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_save(): ... coll = db.test_collection ... doc = {'key': 'value'} ... yield coll.save(doc) ... print 'document _id:', repr(doc['_id']) ... doc['other_key'] = 'other_value' ... yield coll.save(doc) ... yield coll.remove(doc) ... >>> IOLoop.current().run_sync(do_save) document _id: ObjectId('...') Removing Documents ------------------ :meth:`~motor.MotorCollection.remove` takes a query with the same syntax as :meth:`~motor.MotorCollection.find`. :meth:`remove` immediately removes all matching documents. .. doctest:: after-inserting-2000-docs >>> @gen.coroutine ... def do_remove(): ... coll = db.test_collection ... n = yield coll.count() ... print n, 'documents before calling remove()' ... result = yield db.test_collection.remove({'i': {'$gte': 1000}}) ... print (yield coll.count()), 'documents after' ... >>> IOLoop.current().run_sync(do_remove) 2000 documents before calling remove() 1000 documents after .. mongodoc:: remove Commands -------- Besides the "CRUD" operations--insert, update, remove, and find--all other operations on MongoDB are commands. Run them using the :meth:`~motor.MotorDatabase.command` method on :class:`~motor.MotorDatabase`: .. doctest:: after-inserting-2000-docs >>> from bson import SON >>> @gen.coroutine ... def use_count_command(): ... response = yield db.command(SON([("count", "test_collection")])) ... print 'response:', response ... >>> IOLoop.current().run_sync(use_count_command) response: {u'ok': 1.0, u'n': 1000.0} Since the order of command parameters matters, don't use a Python dict to pass the command's parameters. Instead, make a habit of using :class:`bson.SON`, from the ``bson`` module included with PyMongo:: yield db.command(SON([("distinct", "test_collection"), ("key", "my_key"])) Many commands have special helper methods, such as :meth:`~motor.MotorDatabase.create_collection` or :meth:`~motor.MotorCollection.aggregate`, but these are just conveniences atop the basic :meth:`command` method. .. mongodoc:: commands Further Reading --------------- The handful of classes and methods introduced here are sufficient for daily tasks. The API documentation for :class:`~motor.MotorClient`, :class:`~motor.MotorReplicaSetClient`, :class:`~motor.MotorDatabase`, :class:`~motor.MotorCollection`, and :class:`~motor.MotorCursor` provides a reference to Motor's complete feature set. Learning to use the MongoDB driver is just the beginning, of course. For in-depth instruction in MongoDB itself, see `The MongoDB Manual`_. .. _The MongoDB Manual: http://docs.mongodb.org/manual/ .. [#max_concurrent] ``max_concurrent`` is set when creating a :class:`~motor.MotorClient` or :class:`~motor.MotorReplicaSetClient`.