You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all: Is this project maintained? 285 open issues, 40 open pull requests, foreign keys not implemented, serialization and hydration of BSONArray non-existant (oneToMany). These are all very basic requirements for production ready orm.
Due to issue of foreign keys being saved as strings instead of objectid, relations between mongodb documents are effectively non-functional, documentation suggest otherwise.
This results in package being integrated in project which results only with headaches for everyone involved, as soon as they see that relationships are pure cosmetics. Especially so from read context.
This issue has been reported again and again, there is even a pr #1523 that got lost in the crowd of 40 (at the time of writing) open pull requests.
Then you decide to use raw queries and cast objectId to string and vice versa, depending on requirements. Great, fixed.
Moments later you figure out that with oneToMany relations do not get hydrated, again undocumented. Setting up type map for connection, again produces no results as hydrator does not know what to do with simple array.
Has anyone figured out at least a hack, if there is no proper solution, for these scenarios?
Is there a plan to document missing features so that developers in the future do not get caught in this honey trap ?
Is there a fork out there that took care of these issues?
The text was updated successfully, but these errors were encountered:
First of all: Is this project maintained? 285 open issues, 40 open pull requests, foreign keys not implemented, serialization and hydration of BSONArray non-existant (oneToMany). These are all very basic requirements for production ready orm.
Due to issue of foreign keys being saved as strings instead of objectid, relations between mongodb documents are effectively non-functional, documentation suggest otherwise.
This results in package being integrated in project which results only with headaches for everyone involved, as soon as they see that relationships are pure cosmetics. Especially so from read context.
This issue has been reported again and again, there is even a pr #1523 that got lost in the crowd of 40 (at the time of writing) open pull requests.
Then you decide to use raw queries and cast objectId to string and vice versa, depending on requirements. Great, fixed.
Moments later you figure out that with oneToMany relations do not get hydrated, again undocumented. Setting up type map for connection, again produces no results as hydrator does not know what to do with simple array.
Has anyone figured out at least a hack, if there is no proper solution, for these scenarios?
Is there a plan to document missing features so that developers in the future do not get caught in this honey trap ?
Is there a fork out there that took care of these issues?
The text was updated successfully, but these errors were encountered: