Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Can't Fix
-
Affects Version/s: 2.3.2
-
Fix Version/s: None
-
Component/s: ORM
-
Security Level: All
-
Labels:None
Description
We are using Doctringe since 2.2.2.
We the follow relation:
manyToMany:
categories:
targetEntity: \Application\Model\Db\Entity\Category
inversedBy: topics
joinTable:
name: finq_topic_category
joinColumns:
topic_id:
referencedColumnName: id
inverseJoinColumns:
category_id:
referencedColumnName: id
As expected the generated methods in our entities were named like:
addCategory()
getCategories()
...
After we updated to 2.3.2 we got the follow method names:
addCategorie()
getCateogires()
I found in the changelog some notes like "changed naming strategy".
Took us several hours too find out that we had to downgrade back to
2.2.2. Is this a bug or "just" a new behavior?
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Can't Fix [ 7 ] |
- Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DDC-2296, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
Its "just" a new behavior, sadly non BC. The EntityGenerator is really a mess in that regard, because its very hard to test as well. However all the methods are "protected", so you should be able to extend it with your custom entity generator and fixing it.
We are slowly deprecating the EntityGenerator, because this kind of problem and its huge monolithic structure makes it so hard to use and customize.