Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 6419bb6

Browse filesBrowse files
javiereguiluzjaviereguiluz
committed
minor #11227 Correct many-to-many to many-to-one (exastion)
This PR was merged into the 3.4 branch. Discussion ---------- Correct many-to-many to many-to-one <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/roadmap for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `master` for features of unreleased versions). --> Commits ------- d7cc365 Correct many-to-many to many-to-one
2 parents 36399b5 + d7cc365 commit 6419bb6
Copy full SHA for 6419bb6

File tree

1 file changed

+1
-1
lines changed
Filter options

1 file changed

+1
-1
lines changed

‎form/form_collections.rst

Copy file name to clipboardExpand all lines: form/form_collections.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -636,7 +636,7 @@ the relationship between the removed ``Tag`` and ``Task`` object.
636636
``Tag`` is properly removed.
637637

638638
In Doctrine, you have two sides of the relationship: the owning side and the
639-
inverse side. Normally in this case you'll have a many-to-many relationship
639+
inverse side. Normally in this case you'll have a many-to-one relationship
640640
and the deleted tags will disappear and persist correctly (adding new
641641
tags also works effortlessly).
642642

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.