RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-01-18 14:31:40 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #866 from bountin/doc_refresh

Browse Source 
Mentioning the 'refresh' cascading property in the documentation list
This commit is contained in:
Marco Pivetta 2013-12-01 14:07:21 -08:00
commit 3caf1fdfa6
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/en/reference/working-with-associations.rst
View File

@ -403,7 +403,7 @@ There are two approaches to handle this problem in your code:
Transitive persistence / Cascade Operations Transitive persistence / Cascade Operations
------------------------------------------- -------------------------------------------
Persisting, removing, detaching and merging individual entities can Persisting, removing, detaching, refreshing and merging individual entities can
become pretty cumbersome, especially when a highly interweaved object graph become pretty cumbersome, especially when a highly interweaved object graph
is involved. Therefore Doctrine 2 provides a is involved. Therefore Doctrine 2 provides a
mechanism for transitive persistence through cascading of these mechanism for transitive persistence through cascading of these
@ -419,7 +419,8 @@ The following cascade options exist:
- remove : Cascades remove operations to the associated entities. - remove : Cascades remove operations to the associated entities.
- merge : Cascades merge operations to the associated entities. - merge : Cascades merge operations to the associated entities.
- detach : Cascades detach operations to the associated entities. - detach : Cascades detach operations to the associated entities.
- all : Cascades persist, remove, merge and detach operations to - refresh : Cascades refresh operations to the associated entities.
- all : Cascades persist, remove, merge, refresh and detach operations to
associated entities. associated entities.
.. note:: .. note::