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
{{ message }}
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
Hi, i saw there is an issue on TimelineBundle ODM with new versions of doctrine mongo ODM Bundle since they change behavior of hash field type.
First behavior was like ORM. You set a STRING identifer (ABCD), it'll store a serialization of that. You set an ARRAY identifier (for composite keys), it'll serialize it too.
Setting this as string is great but you'll have to make some changes to supports composite keys.
The text was updated successfully, but these errors were encountered:
Yes, but you could refer to an other stored entities:
Storing TimelineBundle with driver ODM but having user via ORM with composite keys. If you cannot store an array of keys on Component table, on mongo you'll not be able to identify User.
We should repeat the behavior for hash field type in ORM. It's a string field type which is serialized/unserialized.
It could be added on Document/Component.php identifier setter/getter.
Look at #96
The text was updated successfully, but these errors were encountered: