Summary: | AddQueryDialog doesn't support attribute query for NamedQuery | ||
---|---|---|---|
Product: | [WebTools] Dali JPA Tools | Reporter: | Dmitry Geraskov <geraskov> |
Component: | JPA | Assignee: | Neil Hauge <neil.hauge> |
Status: | NEW --- | QA Contact: | |
Severity: | trivial | ||
Priority: | P3 | CC: | neil.hauge |
Version: | 2.2 | Keywords: | helpwanted |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Dmitry Geraskov
2009-07-09 02:40:44 EDT
We try to keep the dialogs very simple in the Dali UI, in this case keeping the query entry in the form versus the dialog. This does result in an error situation, so I see your point in entering the bug. I think in this case it is better to have the error than to have the user stuck in a modal dialog while they are writing a query. Other thoughts? What if do not make query field mandatory in the dialog? Actually, there is another possible remedy here that solves the error condition and doesn't involve putting the query text area into the dialog. A colleague of mine suggested that we could simply add a template query to the query text when completing the dialog. This query template could be selected by default for easy type-over. So, for a Named or Named Native Query we could populate the query text with: SELECT [select_expression] FROM [entityName] WHERE [conditional_expression] The template could probably be further customized for named or native named, and use the context of the Entity. Good point. You would be able to add CompletionProposals in future. Moving JPA specific bugs to new JPA component in bugzilla. |