This first implementation allows to use persistence constructors with some limitations (see docs).
One of them is that properties used in constructors of domain classes cannot be marked final.
ATM, final fields are skipped by OGM at scanning time.
This should be changed at the OGM level, retaining these final fields as legitimate when they are part of constructor parameters.
For this we have to match field names with constructor parameter names, and thus OGM has to be aware of the parameter names
It is not the case at the moment.
A second pain point is to handle relationships as constructor parameters.
At the moment, the OGM mapping is done in 2 phases : map the nodes, then the relationships (and relationship entites).
Have rels as parameters would require to change the mapping process in OGM. Maybe another option would be to use proxies in order to hydrate entities lazily as they are available.
Nicolas Mervaillie opened DATAGRAPH-1056 and commented
Issue Links:
("duplicates")
Referenced from: commits 11c93dd, 2af6a45, 2803a4f
The text was updated successfully, but these errors were encountered: