From 17650a6100eefebfacb19a40783080d8ddfa1ec3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20Sch=C3=A4dlich?= Date: Thu, 4 Apr 2019 21:23:22 +0200 Subject: [PATCH] Added cross-links to relevant documentation --- docs/en/reference/caching.rst | 2 ++ docs/en/reference/improving-performance.rst | 5 +++++ 2 files changed, 7 insertions(+) diff --git a/docs/en/reference/caching.rst b/docs/en/reference/caching.rst index b8f956f4a6f..4c07e1607c5 100644 --- a/docs/en/reference/caching.rst +++ b/docs/en/reference/caching.rst @@ -282,6 +282,8 @@ You can set the namespace a cache driver should use by using the setNamespace('my_namespace_'); +.. _integrating-with-the-orm: + Integrating with the ORM ------------------------ diff --git a/docs/en/reference/improving-performance.rst b/docs/en/reference/improving-performance.rst index d19b6947732..be4ac0acb5a 100644 --- a/docs/en/reference/improving-performance.rst +++ b/docs/en/reference/improving-performance.rst @@ -26,6 +26,8 @@ Doctrine will need to load your mapping information on every single request and has to parse each DQL query on every single request. This is a waste of resources. +See :ref:`integrating-with-the-orm` + Alternative Query Result Formats -------------------------------- @@ -42,6 +44,8 @@ for updates, which means when you call flush on the EntityManager these entities even if properties changed. Read-Only allows to persist new entities of a kind and remove existing ones, they are just not considered for updates. +See :ref:`annref_entity` + Extra-Lazy Collections ---------------------- @@ -61,6 +65,7 @@ Apply Best Practices A lot of the points mentioned in the Best Practices chapter will also positively affect the performance of Doctrine. +See :doc:`Best Practices ` Change Tracking policies ------------------------