Skip to content
This repository was archived by the owner on Sep 16, 2021. It is now read-only.

Add documentation about the 'namespace' option #553

Merged
merged 2 commits into from
Aug 25, 2014
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion reference/configuration/phpcr_odm.rst
Original file line number Diff line number Diff line change
Expand Up @@ -461,6 +461,7 @@ not configure anything here, the ODM services will not be loaded.
instance_class: ~
class: ~
id: ~
namespace: ~


.. code-block:: xml
Expand Down Expand Up @@ -496,6 +497,7 @@ not configure anything here, the ODM services will not be loaded.
instance-class="null"
class="null"
id="null"
namespace="null"
/>
</odm>
</config>
Expand Down Expand Up @@ -528,6 +530,7 @@ not configure anything here, the ODM services will not be loaded.
'instance_class' => null,
'class' => null,
'id' => null,
'namespace' => null,
),
),
));
Expand Down Expand Up @@ -581,7 +584,16 @@ names without any actual configuration.
metadata_cache_driver
"""""""""""""""""""""

Configure a cache driver for the Doctrine metadata. This is the same as for `Doctrine ORM`_.
Configure a cache driver for the Doctrine metadata. This is the same as for
`Doctrine ORM`_.

The ``namespace`` value is useful if you are using one primary caching server
for multiple sites that have similar code in their respective ``vendor/``
directories. By default, Symfony will try to generate a unique namespace
value for each application but if code is very similar between two
applications, it is very easy to have two applications share the same
namespace. This option also prevents Symfony from needing to re-build
application cache on each Composer update on a newly generated namespace.

General Settings
~~~~~~~~~~~~~~~~
Expand Down