doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-24 06:52:09 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

Add documentation about ClassMetadata::getAssociationMapping in 3.0 Upgrade Note #6478

New Issue
Closed
opened 2026-01-22 15:33:50 +01:00 by admin · 1 comment
admin commented 2026-01-22 15:33:50 +01:00
Owner
Copy Link

Originally created by @VincentLanglet on GitHub (May 31, 2020).

Support Question

I'm trying to do a refactoring on a massive project an introducing new Interface. I would like to have these interface compatible with both Doctrine 2.x and 3.x.
I mainly work with

  • ClassMetaData::$fieldMappings
  • ClassMetaData::$associationMappings

I saw that both getFieldMappings and getAssociationMappings are removed in ClassMetaData.

When I read the Upgrade note,
https://github.com/doctrine/orm/blob/master/UPGRADE.md#bc-break-removed-methods-in-classmetadata-1
there is a mention about ClassMetadata::getFieldMapping but none about ClassMetadata::getAssociationMapping or ClassMetaData::ONE_TO_ONE, ClassMetaData::ONE_TO_MANY, ClassMetaData::MANY_TO_ONE and ClassMetaData::MANY_TO_MANY constants.

Where can I find some explanations about the migration ?
Does supporting both doctrine 2.x and 3.x on a project will be easy if I work with these properties ?

Originally created by @VincentLanglet on GitHub (May 31, 2020). ### Support Question I'm trying to do a refactoring on a massive project an introducing new Interface. I would like to have these interface compatible with both Doctrine 2.x and 3.x. I mainly work with - ClassMetaData::$fieldMappings - ClassMetaData::$associationMappings I saw that both `getFieldMappings` and `getAssociationMappings` are removed in ClassMetaData. When I read the Upgrade note, https://github.com/doctrine/orm/blob/master/UPGRADE.md#bc-break-removed-methods-in-classmetadata-1 there is a mention about `ClassMetadata::getFieldMapping` but none about `ClassMetadata::getAssociationMapping` or `ClassMetaData::ONE_TO_ONE`, `ClassMetaData::ONE_TO_MANY`, `ClassMetaData::MANY_TO_ONE` and `ClassMetaData::MANY_TO_MANY` constants. Where can I find some explanations about the migration ? Does supporting both doctrine 2.x and 3.x on a project will be easy if I work with these properties ?
admin closed this issue 2026-01-22 15:33:51 +01:00
admin commented 2026-01-22 15:33:52 +01:00
Author
Owner
Copy Link

@beberlei commented on GitHub (Jun 4, 2020):

@VincentLanglet don't waste your time on doctrine 3 support now, nothing is set in stone yet, please build against 2.* and we will work on upgrade path as we get there (far out).

@beberlei commented on GitHub (Jun 4, 2020): @VincentLanglet don't waste your time on doctrine 3 support now, nothing is set in stone yet, please build against 2.* and we will work on upgrade path as we get there (far out).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6478
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?