[JBoss JIRA] (TEIIDDES-1436) Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1436?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1436:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=920279
> Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1436
> URL: https://issues.jboss.org/browse/TEIIDDES-1436
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7.1
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: foo.zip
>
>
> "Document models can be created that have nested namespaces, and Teiid contains code to use different namespace prefixes for nested elements. However at least for my simple test case (see attached) the generated mapping document does not contain any namespaceURI information for the elements - it only has the namespace declarations. It would appear that the logic in MappingDocumentFormatter is not correctly associating the prefix/uri with elements at least for a simple hand made document model. I don't know if things are different when starting with a schema." - SteveH
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1436) Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1436?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1436:
--------------------------------
Issue Type: Bug (was: Feature Request)
> Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1436
> URL: https://issues.jboss.org/browse/TEIIDDES-1436
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7.1
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: foo.zip
>
>
> "Document models can be created that have nested namespaces, and Teiid contains code to use different namespace prefixes for nested elements. However at least for my simple test case (see attached) the generated mapping document does not contain any namespaceURI information for the elements - it only has the namespace declarations. It would appear that the logic in MappingDocumentFormatter is not correctly associating the prefix/uri with elements at least for a simple hand made document model. I don't know if things are different when starting with a schema." - SteveH
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1614.
---------------------------------------
Resolution: Done
> Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1614
> URL: https://issues.jboss.org/browse/TEIIDDES-1614
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Validation
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
> Attachments: DynamicSQLMPS.zip
>
>
> Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT * FROM PARTS;
> END
> Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated.
> When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1614:
-------------------------------------------
The cause of this is the setting of the CreateProcedureCommand's projected symbols collection as empty rather than null. The problem is 2 pronged:
a) New Teiid code in the 8.2 release sets it to empty
b) Designer's TransformValidator sets it to empty due to the 7.7/8.2 migration
A fix for the first has been added to Teiid's 8.3 codestream, see [this commit|https://github.com/Teiid-Designer/teiid/commit/ddbe94c61b3432fcc7f...]
A fix for the second is more problematic since the project symbols added from the TransformValidator come from the EObject side of Designer. Thus, some method needs to pass them in. This is achieved by adding a postResolveCommand method to the IQueryResolver spi interface and accompanying implementations.
In the 7.7.x implementation of the IQueryResolver, the original if statement can be restored to its original state and should function correctly, according to the original fix
added due to [TEIIDES-624|https://issues.jboss.org/browse/TEIIDDES-624].
> Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1614
> URL: https://issues.jboss.org/browse/TEIIDDES-1614
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Validation
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
> Attachments: DynamicSQLMPS.zip
>
>
> Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT * FROM PARTS;
> END
> Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated.
> When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1531) Exception when updating Oracle NVARCHAR2 columns
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1531?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1531:
----------------------------------------
The following type check is currently in place. I imported from BQT2 (SQL SERVER) and a column with VARCHAR2 was imported as string() datatype.
So I think this is already implemented.
{code:title=OracleModelProcessor.java|borderStyle=solid}
protected EObject findType( final String jdbcTypeName,
final List problems ) {
String standardName = jdbcTypeName;
if (VARCHAR2_TYPE_NAME.equalsIgnoreCase(jdbcTypeName) || NVARCHAR2_TYPE_NAME.equalsIgnoreCase(jdbcTypeName)) {
standardName = RelationalTypeMapping.SQL_TYPE_NAMES.VARCHAR;
}
return super.findType(standardName, problems);
}
{code}
> Exception when updating Oracle NVARCHAR2 columns
> ------------------------------------------------
>
> Key: TEIIDDES-1531
> URL: https://issues.jboss.org/browse/TEIIDDES-1531
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Environment: Windows 7 64 bit, Eclipse Indigo, Oracle jdbc thin 11.2.0.2.0
> Reporter: I Leitch
> Assignee: Mark Drilling
> Fix For: 8.1
>
>
> If it doesn't already do so, the Oracle importer should import NVARCHAR2 (type 1111) and VARCHAR2 (type 12) as string.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1614:
-----------------------------------
Attachment: DynamicSQLMPS.zip
> Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1614
> URL: https://issues.jboss.org/browse/TEIIDDES-1614
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Validation
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
> Attachments: DynamicSQLMPS.zip
>
>
> Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT * FROM PARTS;
> END
> Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated.
> When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1614:
-----------------------------------
Description:
Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PARTS;
END
Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated.
When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type
was:
Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PARTS;
END
Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated.
> Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1614
> URL: https://issues.jboss.org/browse/TEIIDDES-1614
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Validation
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following:
> CREATE VIRTUAL PROCEDURE
> BEGIN
> SELECT * FROM PARTS;
> END
> Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated.
> When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month