[
https://issues.apache.org/jira/browse/QPID-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407482#comment-15407482
]
Keith Wall commented on QPID-7377:
----------------------------------
The algorithm will need to cope with discovering the type of the attributes
that are not declared on the category. It will need to walk the categories
tree to discover the type of such attributes. Identically named attributes on
sub-types that have different type definitions will cause a problem, but these
should probably be disallowed ( as the model is validated on startup?).
> Query results should carry type meta-information
> ------------------------------------------------
>
> Key: QPID-7377
> URL: https://issues.apache.org/jira/browse/QPID-7377
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Priority: Minor
>
> Currently the Query UI within the WMC needs to know the type of the columns
> within query result sets in order to present attributes of types such as
> list, set etc correctly within the grid results. It does this currently by
> matching column names within the results to the configured object's attribute
> level metadata. This is fragile approach and will fail if say, a user
> chose to rename a column within a results set or the query references a
> parent attributes.
> Just like JDBC result sets have metadata, it would be desirable if query
> results carried metadata too. Derived column values i.e. those resulting
> from expressions or functions may be problematic but Object would probably
> suffice for now.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
