properly specify semantics of path expressions #81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
njr-11
approved these changes
Oct 8, 2025
Co-authored-by: Nathan Rauh <[email protected]>
otaviojava
approved these changes
Oct 9, 2025
gavinking
commented
Oct 9, 2025
|
|
||
| If any element of a path expression evaluates to a null value, the whole path expression evaluates to a null value. | ||
|
|
||
| NOTE: An implementation of the core language is not required to support path expressions which involve multiple entities. For example, if `Book` and `Publisher` are different entity types, then the path expression `book.publisher.name` is not part of the core language.footnote:[Path expressions involving multiple entities are called _implicit joins_ by the Jakarta Persistence specification.] |
There was a problem hiding this comment.
@otaviojava I'm adding this NOTE to address #86.
There was a problem hiding this comment.
On non-relational databases, this kind of navigation is usually implicit, since related data is stored within the same aggregate.
The note makes sense overall.
There was a problem hiding this comment.
On non-relational databases, this kind of navigation is usually implicit, since related data is stored within the same aggregate.
We would consider that navigation from a root entity to its embeddable, not navigation between entities, I think.
|
Made a couple of improvements and moved this out of draft mode. |
otaviojava
approved these changes
Oct 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #74.