Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expression parser to support path aliases #657

Closed
andrus opened this issue Oct 7, 2023 · 0 comments · Fixed by #671
Closed

Expression parser to support path aliases #657

andrus opened this issue Oct 7, 2023 · 0 comments · Fixed by #671
Milestone

Comments

@andrus
Copy link
Contributor

andrus commented Oct 7, 2023

Paths with aliases (a.b#alias1.c) should be properly parsed and translated to Cayenne expressions. This would allow to build special kinds of expressions:

// "either 5 or 6" (no aliases)
a.b = 5 or a.b = 6

// "both 5 and 6" (will never match anything without aliases)
a.b = 5 and a.b = 6

// "both 5 and 6" (with aliases)
a.b#a1 = 5 and a.b#a2 = 6`

ExpPath after parsing should contain a normalized path without aliases and a map of aliases. When translating to Cayenne, the aliases must be passed over to ASTObjPath

@andrus andrus changed the title Expression to Cayenne translation should support path aliases Expression parser to support path aliases Oct 7, 2023
stariy95 added a commit that referenced this issue Feb 12, 2024
Expression parser to support path aliases. Fixes #657.
stariy95 added a commit that referenced this issue Feb 12, 2024
#657 Expression parser to support path aliases
@stariy95 stariy95 added this to the 5.0-M20 milestone Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants