@@ -35,8 +35,8 @@ of your project:
35
35
.. code-block :: text
36
36
37
37
DoctrineMongoDBBundle /bundles/Symfony/Bundle git://github.com/symfony/DoctrineMongoDBBundle.git
38
- mongodb-odm / git://github.com/doctrine/mongodb-odm.git
39
- mongodb / git://github.com/doctrine/mongodb.git
38
+ doctrine- mongodb-odm / git://github.com/doctrine/mongodb-odm.git
39
+ doctrine- mongodb / git://github.com/doctrine/mongodb.git
40
40
41
41
Now, update the vendor libraries by running:
42
42
@@ -51,8 +51,8 @@ Be sure to add them anywhere *above* the ``Doctrine`` namespace (shown here)::
51
51
// app/autoload.php
52
52
$loader->registerNamespaces(array(
53
53
// ...
54
- 'Doctrine\\ODM\\MongoDB' => __DIR__.'/../vendor/mongodb-odm/lib',
55
- 'Doctrine\\MongoDB' => __DIR__.'/../vendor/mongodb/lib',
54
+ 'Doctrine\\ODM\\MongoDB' => __DIR__.'/../vendor/doctrine- mongodb-odm/lib',
55
+ 'Doctrine\\MongoDB' => __DIR__.'/../vendor/doctrine- mongodb/lib',
56
56
'Doctrine' => __DIR__.'/../vendor/doctrine/lib',
57
57
// ...
58
58
));
@@ -251,10 +251,10 @@ doesn't replace your existing methods).
251
251
252
252
.. note ::
253
253
254
- Doctrine doesn't care whether your properties are ``public ``, `` protected ``
255
- or `` private ``, or whether or not you have a getter or setter function
256
- for a property. The getters and setters are generated here only because
257
- you'll need them to interact with your PHP object.
254
+ Doctrine doesn't care whether your properties are ``protected `` or `` private ``,
255
+ or whether or not you have a getter or setter function for a property.
256
+ The getters and setters are generated here only because you'll need them
257
+ to interact with your PHP object.
258
258
259
259
Persisting Objects to MongoDB
260
260
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -309,9 +309,9 @@ Let's walk through this example:
309
309
310
310
.. note ::
311
311
312
- In fact, since Doctrine is aware of all your managed objects, when you
313
- call the ``flush() `` method, it calculates an overall changeset and executes
314
- the most efficient operation possible.
312
+ In fact, since Doctrine is aware of all your managed objects, when you
313
+ call the ``flush() `` method, it calculates an overall changeset and executes
314
+ the most efficient operation possible.
315
315
316
316
When creating or updating objects, the workflow is always the same. In the
317
317
next section, you'll see how Doctrine is smart enough to update entries if
0 commit comments