|
As most NoSQL stores don't support referential integrity natively, it may happen that a persisted association refers to a non-existent record.
Currently, loading the associating entity fails in that case:
HHH000327: Error performing load command : org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [...]
The user can ignore that failure by specifying @NotFound(action = NotFoundAction.IGNORE) at the association. But they'd effectively have to do this for each association.
So should we implicitly do this, at least on those stores that don't support referential integrity (e.g. it cannot really happen on Neo4j as a relationship must not have a "loose" end)?
|