]
Steven Hawkins updated TEIIDDES-569:
------------------------------------
Attachment: org.teiid.designer.metamodels.relational.patch
The patch adds the SQLXML type handling. It also corrects some of the type mapping logic
SQL Type | Built In
bigint -> Long
bit -> Boolean
char -> String
tinyint -> Byte
Bit and tinyint previously were mapped to short. Bit to boolean is the most appropriate.
The only rationale tinyint to short is if we are trying to compensate for sources that
treat this type as unsigned (MySQL/SQLServer) and automatically widen it. In which case
it's fine to leave it as short, but it's better to detect if the type is signed,
then widen it.
SQLXML type is imported as object
---------------------------------
Key: TEIIDDES-569
URL:
https://jira.jboss.org/browse/TEIIDDES-569
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1
Environment: All
Reporter: Paul Nittel
Assignee: Steven Hawkins
Fix For: 7.1.1
Attachments: org.teiid.designer.metamodels.relational.patch, Validating_Wx.zip
I imported the metadata for the INVOKE function from the weather example VDB. When I used
the function in a transformation (see below), there was a validation error. Steve Hawkins
noted the type of the result procedure parameter was "object" and should be
"SQLXML". (Turns out that "SQLXML" is "XMLLiteral" in
current Designer parlance. Perhaps that should be changed... Ask Steve H.)
After several attempts to validate the SQL, it finally validated. (And another Jira is on
the way.)
SELECT
t.*
FROM
(EXEC Wx_Teiid.invoke(binding = null, action = 'GET', request = null, endpoint
= QUERYSTRING('', '38.99,-77.02 39.70,-104.80 47.6,-122.30' AS listLatLon,
'time-series' AS product, '2004-01-01T00:00:00' AS "begin",
'2013-04-20T00:00:00' AS "end", 'maxt' AS maxt, 'mint'
AS mint))) AS w, XMLTABLE('/dwml/data/location' PASSING result COLUMNS
location_key string, lattitude string PATH 'point/@latitude', longitude string
PATH 'point/@longitude') AS t
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: