[
https://issues.jboss.org/browse/TEIIDDES-1467?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1467:
-----------------------------------
Description:
TEIIDDES-1456 created a requirement to define both view and source model Extension
Properties in the same MED but still need to filter what a user sees and can edit in the
properties view.
native-query property on Procedures, applies to PHYSICAL model
non-prepared and deterministic properties applies to PHYSICAL model
For physial procedures with "is function == TRUE", the function extension
properties need to get displayed for editing in properties view. So there needs to be some
wiring/listening to refresh when properties changed or are originally loaded. Again, the
Assistant class seems like the logic place to delegate the logic to.
By adding method to ModelExtensionAssistant class,
ModelExtensionAssisantAggregator.getPropertyDefinitions(EObject) method could handle the
filtering.
was:
TEIIDDES-1456 created a requirement to define both view and source model Extension
Properties in the same MED but still need to filter what a user sees and can edit in the
properties view.
native-query property on Procedures, applies to both VIRTUAL and PHYSICAL models
non-prepared and deterministic properties applies to ONLY PHYSICAL models
By adding method to ModelExtensionAssistant class,
ModelExtensionAssisantAggregator.getPropertyDefinitions(EObject) method could handle the
filtering.
Add method to MED assistant class to allow passing object to retrieve
property descriptors
------------------------------------------------------------------------------------------
Key: TEIIDDES-1467
URL:
https://issues.jboss.org/browse/TEIIDDES-1467
Project: Teiid Designer
Issue Type: Feature Request
Affects Versions: 8.0
Reporter: Barry LaFond
Assignee: Dan Florian
Priority: Critical
Fix For: 8.0
Attachments: relational.mxd
TEIIDDES-1456 created a requirement to define both view and source model Extension
Properties in the same MED but still need to filter what a user sees and can edit in the
properties view.
native-query property on Procedures, applies to PHYSICAL model
non-prepared and deterministic properties applies to PHYSICAL model
For physial procedures with "is function == TRUE", the function extension
properties need to get displayed for editing in properties view. So there needs to be some
wiring/listening to refresh when properties changed or are originally loaded. Again, the
Assistant class seems like the logic place to delegate the logic to.
By adding method to ModelExtensionAssistant class,
ModelExtensionAssisantAggregator.getPropertyDefinitions(EObject) method could handle the
filtering.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira