[JBoss JIRA] Created: (TEIIDDES-892) Editing Description sometimes fails because of focus issues
by Barry LaFond (JIRA)
Editing Description sometimes fails because of focus issues
-----------------------------------------------------------
Key: TEIIDDES-892
URL: https://issues.jboss.org/browse/TEIIDDES-892
Project: Teiid Designer
Issue Type: Bug
Components: Views
Affects Versions: 7.3
Reporter: Barry LaFond
Fix For: 7.4
The Description View allows users to set ... Description text for most/all EObjects or model objects.
But the actually committing of the EMF transaction doesn't happen until there is an unfocus on that view. Sometimes the change/edit will NOT commit and that's not good. We did this because we didn't want to commit each edit during keystroke events.
I think a better option would be to make the Description view READ ONLY and add an "Edit..." or "Change..." button to open a separate dialog. On Dialog "okFinish()" we would create/commit a transaction thereby insuring that we always commit.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (TEIIDDES-210) Add implicit conversion of NULL to correct datatype in transformation validator
by Marc Shirley (JIRA)
Add implicit conversion of NULL to correct datatype in transformation validator
-------------------------------------------------------------------------------
Key: TEIIDDES-210
URL: https://jira.jboss.org/jira/browse/TEIIDDES-210
Project: Teiid Designer
Issue Type: Feature Request
Components: Transformations, Validation
Affects Versions: 6.0.0, 6.1.0
Reporter: Marc Shirley
When using NULL value as a column (ie, NULL as columnName), it is only implicitly converted to a string. When trying to use the NULL as a column of type date, integer, float, etc., the validator throws a warning that the transformation is not valid. If you wrap the NULL in a convert to the correct column datatype (ie, "convert(NULL,date)"), the transformation can be validated successfully.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Resolved: (TEIIDDES-893) Resolving changes to consolidate teiid/teiid designer handling
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-893?page=com.atlassian.jira.plug... ]
Steven Hawkins resolved TEIIDDES-893.
-------------------------------------
Resolution: Done
Added a resolving hook that takes the contextual information of what group and command type is being resolved. Teiid can then derive the appropriate metadata, in the same logic as is used for the engine.
Temporary patching code was added to teiid_embedded_query.
Also corrected the ModelerMetadata search logic so that entries that have not yet been created in an index are still found, which also allowed SqlTransformationInfo to allow null sql.
Removed extranous methods related to XQuery handling, but left the metamodel in place until it is needed to be removed.
> Resolving changes to consolidate teiid/teiid designer handling
> --------------------------------------------------------------
>
> Key: TEIIDDES-893
> URL: https://issues.jboss.org/browse/TEIIDDES-893
> Project: Teiid Designer
> Issue Type: Task
> Affects Versions: 7.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 7.4
>
>
> Designer currently must supply external metadata that should be easily derived by Teiid.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Commented: (TEIIDDES-792) add support for in/out out return params
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-792?page=com.atlassian.jira.plug... ]
Steven Hawkins commented on TEIIDDES-792:
-----------------------------------------
Changed the code to allow inout/out/return parameters for virtual procedures. The restrictions were removed that forced virtual procs to have resultsets. Also changed the default sql for generated procedures to not wrap with a select and to use named parameters, e.g.
instead of
create virtual procedure
begin
select * from (exec foo(param1, param2)) as proc
end
we'll get
create virtual procedure
begin
exec foo(param1=>param1, param2=>param2)
end
this allows for proper handling of out/inout/return assignment. The docs and the test scripts will need updated appropriately.
The code for text based metadata import and export was not updated. That code still assumes that procedures have result sets.
> add support for in/out out return params
> ----------------------------------------
>
> Key: TEIIDDES-792
> URL: https://issues.jboss.org/browse/TEIIDDES-792
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 7.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 7.4
>
>
> In/out, out, return parameters are supported by Teiid virtual procedures - not just result sets - as of 7.4. Designer should remove validation restrictions preventing the usage of these parameters and update the external metadata logic to add out/return parameters as valid symbols.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months