Andrey Razumovsky commented on CAY-888:
---------------------------------------
While #2 and #3 subtasks are plain and simple, the first one is more complicated. The problem is that Expression.fromString() succeeds without any exceptions even if some attributes are typed wrong and absent in entity (and that seems to be Users' main headache). So the only think i can suggest here is to iterate through AST tree and check ASTPath nodes.
What do you think about this idea? Otherwise, we'll be able to perform only weak checking (and it already exists, actually).
> CM Usability: Object Select Query Improvements
> ----------------------------------------------
>
> Key: CAY-888
> URL: https://issues.apache.org/cayenne/browse/CAY-888
> Project: Cayenne
> Issue Type: New Feature
> Components: CayenneModeler GUI
> Reporter: Thomas Bernhard
> Assignee: Kevin Menard
>
> Object Select Query UI should be smarter and more usable:
> #1 Qualifier field shouldn't be just a dummy text filed. It should be smarter, with validations, or even some sort of completion
> or live checking so that the user quickly can do what he wants and be sure that it's OK. Because this dummy field is very error prone, many CM users avoid "Named Queries". I must admint - even myself - I always type something wrong there.
> #2 When selecting a QueryRoot -> e.g to Person, than the Query Name should be changed too to "PersonQuery", but only in the case the user hasn't manually changed that field to something else than the default generated by CM at dialog open. This is very user friendly (many IDEs offer such "variable suggestion").
> #3 Orderings and Prefetches tab panes should use a JSplitPane to separte the upper and the lower zones. For entities with many fields, the users always have to scroll because one can't simply drag a split pane to adapt the size.
-- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
This archive was generated by hypermail 2.0.0 : Thu May 29 2008 - 01:18:21 EDT