Skip to content

Conversation

greg0ire
Copy link
Member

This field only makes sense for the owning side of many-to-many mappings. Moving it down allows us to make it non-nullable.

@greg0ire
Copy link
Member Author

greg0ire commented Apr 17, 2023

At this point you're probably wondering why I'm not pushing the switch to the object API of the association mapping… well, it comes with lots of errors. In this cases, it's revealing a flaw in my design, so that's good I guess, and we shouldn't add the errors to the baseline too quickly. I'm going to do small PRs that should prevent some of them from ever showing up.

This field only makes sense for the owning side of many-to-many
mappings. Moving it down allows us to make it non-nullable.
@greg0ire greg0ire force-pushed the join-table-columns-down branch from a23d288 to 49cc83d Compare April 17, 2023 19:45
-
message: "#^Access to an undefined property Doctrine\\\\ORM\\\\Mapping\\\\AssociationMapping\\:\\:\\$joinTableColumns\\.$#"
path: lib/Doctrine/ORM/Persisters/Collection/ManyToManyPersister.php

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is caused by the issue already linked line 27

@greg0ire greg0ire merged commit fd64e13 into doctrine:3.0.x Apr 17, 2023
@greg0ire greg0ire added this to the 3.0.0 milestone Apr 17, 2023
@greg0ire greg0ire deleted the join-table-columns-down branch April 17, 2023 20:56
@greg0ire greg0ire mentioned this pull request Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants