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
For instance, for the https://github.com/arangodb/spring-data#reference
example, when address.id is null, it's not currently auto-persisted; thus it currently has to be persisted separately (prior to persisting the parent entity). In JPA implementations i've worked with, the association(s) would be auto-persisted (allowing to persist an entire aggregate[1] by making only 1 call to persist the aggregate root).
I think it would be beneficial (for users & ArangoDB) if arangodb/spring-data functioned similarly: it would make development easier, & facilitate adoption of ArangoDB. The implementation also shouldn't be difficult...
The text was updated successfully, but these errors were encountered:
haqer1
changed the title
Auto-persistence of null associations would be beneficial (for users & ArangoDB)
Auto-persistence of associations with null ids would be beneficial (for users & ArangoDB)
Feb 12, 2018
For instance, for the
https://github.com/arangodb/spring-data#reference
example, when address.id is null, it's not currently auto-persisted; thus it currently has to be persisted separately (prior to persisting the parent entity). In JPA implementations i've worked with, the association(s) would be auto-persisted (allowing to persist an entire aggregate[1] by making only 1 call to persist the aggregate root).
I think it would be beneficial (for users & ArangoDB) if arangodb/spring-data functioned similarly: it would make development easier, & facilitate adoption of ArangoDB. The implementation also shouldn't be difficult...
[1] https://martinfowler.com/bliki/DDD_Aggregate.html
The text was updated successfully, but these errors were encountered: