[
https://issues.apache.org/jira/browse/CAY-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834809#action_12834809
]
Andrus Adamchik commented on CAY-1213:
--------------------------------------
Ksenia looked at this a bit , and it turns out that:
1. Our EJBQL implementation doesn't process enums properly.
2. In Expression API (unless we decide to add a special prefix for enums),
there is a syntactic ambiguity between a relationship path and an enum.
For now the plan is to fix #1 and keep the #2 ambiguity, resolving it when
expression is processed. I.e. ASTPath can be a path or an enum.
> Cayenne should support enum types in qualifier statements/expression handling
> -----------------------------------------------------------------------------
>
> Key: CAY-1213
> URL: https://issues.apache.org/jira/browse/CAY-1213
> Project: Cayenne
> Issue Type: Improvement
> Components: Core Library
> Affects Versions: 3.0M5
> Reporter: Robert Zeigler
> Assignee: Robert Zeigler
> Fix For: Undefined future
>
>
> Currently, cayenne doesn't support java enums in its expression syntax and,
> by extension, in qualifier statements. This makes it impossible to use an
> enum type as a class descriminator for inheritance.
> Enum expressions would look like:
> propertyName = some.package.Type.CONSTANT
> to make it consistent with JPA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
