[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2018:
----------------------------------------
TEIID DDL from BQT2 (SqlServer) ALL_TYPES table:
CREATE FOREIGN TABLE "bqt2.BQT2.ALL_TYPES" (
type_int integer OPTIONS (NAMEINSOURCE '"type_int"', NATIVE_TYPE 'int'),
type_integer integer OPTIONS (NAMEINSOURCE '"type_integer"', NATIVE_TYPE 'int'),
type_smallint short OPTIONS (NAMEINSOURCE '"type_smallint"', NATIVE_TYPE '…
[View More]smallint'),
type_tinyint short OPTIONS (NAMEINSOURCE '"type_tinyint"', NATIVE_TYPE 'tinyint'),
type_decimal bigdecimal(18,2147483647) OPTIONS (NAMEINSOURCE '"type_decimal"', NATIVE_TYPE 'decimal'),
type_decimal_5 bigdecimal(5,2147483647) OPTIONS (NAMEINSOURCE '"type_decimal_5"', NATIVE_TYPE 'decimal'),
type_decimal_5_5 bigdecimal(5,2147483647) OPTIONS (NAMEINSOURCE '"type_decimal_5_5"', NATIVE_TYPE 'decimal'),
type_double_precision double OPTIONS (NAMEINSOURCE '"type_double_precision"', RADIX 2, NATIVE_TYPE 'float'),
type_float double OPTIONS (NAMEINSOURCE '"type_float"', RADIX 2, NATIVE_TYPE 'float'),
type_float_10 float OPTIONS (NAMEINSOURCE '"type_float_10"', RADIX 2, NATIVE_TYPE 'real'),
type_numeric bigdecimal(18,2147483647) OPTIONS (NAMEINSOURCE '"type_numeric"', NATIVE_TYPE 'numeric'),
type_numeric_5 bigdecimal(5,2147483647) OPTIONS (NAMEINSOURCE '"type_numeric_5"', NATIVE_TYPE 'numeric'),
type_numeric_5_5 bigdecimal(5,2147483647) OPTIONS (NAMEINSOURCE '"type_numeric_5_5"', NATIVE_TYPE 'numeric'),
type_real float OPTIONS (NAMEINSOURCE '"type_real"', RADIX 2, NATIVE_TYPE 'real'),
type_bit boolean OPTIONS (NAMEINSOURCE '"type_bit"', RADIX 0, NATIVE_TYPE 'bit'),
type_character string(1) OPTIONS (NAMEINSOURCE '"type_character"', NATIVE_TYPE 'char'),
type_character_10 string(10) OPTIONS (NAMEINSOURCE '"type_character_10"', NATIVE_TYPE 'char'),
type_char string(1) OPTIONS (NAMEINSOURCE '"type_char"', NATIVE_TYPE 'char'),
type_char_10 string(10) OPTIONS (NAMEINSOURCE '"type_char_10"', NATIVE_TYPE 'char'),
type_nchar string(1) OPTIONS (NAMEINSOURCE '"type_nchar"', CHAR_OCTET_LENGTH 2, NATIVE_TYPE 'nchar'),
type_nchar_10 string(10) OPTIONS (NAMEINSOURCE '"type_nchar_10"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'nchar'),
type_varchar string(1) OPTIONS (NAMEINSOURCE '"type_varchar"', NATIVE_TYPE 'varchar'),
type_varchar_10 string(10) OPTIONS (NAMEINSOURCE '"type_varchar_10"', NATIVE_TYPE 'varchar'),
type_long_nvarchar string(1) OPTIONS (NAMEINSOURCE '"type_long_nvarchar"', CHAR_OCTET_LENGTH 2, NATIVE_TYPE 'nvarchar'),
type_long_nvarchar_10 string(10) OPTIONS (NAMEINSOURCE '"type_long_nvarchar_10"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'nvarchar'),
type_text clob OPTIONS (NAMEINSOURCE '"type_text"', NATIVE_TYPE 'text'),
type_money bigdecimal(19,2147483647) OPTIONS (NAMEINSOURCE '"type_money"', NATIVE_TYPE 'money'),
type_smallmoney bigdecimal(10,2147483647) OPTIONS (NAMEINSOURCE '"type_smallmoney"', NATIVE_TYPE 'smallmoney'),
type_datetime timestamp OPTIONS (NAMEINSOURCE '"type_datetime"', NATIVE_TYPE 'datetime'),
type_binary varbinary(1) OPTIONS (NAMEINSOURCE '"type_binary"', NATIVE_TYPE 'binary'),
type_binary_2 varbinary(2) OPTIONS (NAMEINSOURCE '"type_binary_2"', NATIVE_TYPE 'binary'),
type_image blob OPTIONS (NAMEINSOURCE '"type_image"', NATIVE_TYPE 'image'),
type_varbinary varbinary(1) OPTIONS (NAMEINSOURCE '"type_varbinary"', NATIVE_TYPE 'varbinary')
) OPTIONS (NAMEINSOURCE '"bqt2"."BQT2"."ALL_TYPES"', UPDATABLE TRUE, CARDINALITY 0);
> DDL importer creates wrong data type for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
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
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2034) Inconsistent model naming validation in wizards and dialogs
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2034?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2034:
----------------------------------------
* Utilized ModelNameChecker.validate() method to add character validation
* In various wizard pages/panels, added prefixes to status message (invalid chars) to add context like "Invalid model name. Character at position '&' is invalid..... "
> Inconsistent model naming validation in wizards and dialogs
> -…
[View More]----------------------------------------------------------
>
> Key: TEIIDDES-2034
> URL: https://issues.jboss.org/browse/TEIIDDES-2034
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3, 8.3.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.4
>
>
> Performed an analysis of Designer's dialog and wizard panels validation of editable model names:
> 1) Refactor > Rename (*OK*)
> - Seems to allow only LETTERS, NUMBERS and '_' char
> - Shows appropriate error message
>
> 2) New Model Wizard (*FIX*)
> - Model name allows any char
>
> 3) Flat File and XML Import Wizards (*FIX*)
> - Source and View model names allow any char
> - View Table name only allows LETTERS, NUMBERS and '_' char
>
> 4) Import > WSDL File or URL >> Source and View Model (SOAP) (*FIX*)
> - Source and View model names allow any char
>
> 5) Import > WSDL File or URL >> Web Service Model (*FIX*)
> - Web Service Model Name allows any char (first page)
> - Schema model name allows any char (Workspace Location Selection page)
> - XML model name allows any char (last page)
>
> 6) JDBC Import wizard Model Name allows any char (*FIX*)
> 7) DDL Import Wizard (*OK*)
> - Appears to be working correctly: Allows only LETTERS, NUMBERS and '_' char
>
> 8) Import > Designer Test File >> Source or View Models (*FIX*)
> - Source and View model names allow any char
> - Utilizes Relational Model Selector dialog
> - Als used in "Create Materailized View Model" dialog
> 9) Create Web Service dialog (*FIX*)
> - schema and WS model names allow any char
>
> 10) Modeling > Create XML View Documents (*FIX*)
> - Select or create XML View model dialog allow any char for New Model Name
> - Similar to Relational Model Selector dialog
>
> 11) Import > Teiid Connection >> Source Model (*FIX*)
> - Source model name allows any char
--
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
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2034) Inconsistent model naming validation in wizards and dialogs
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2034?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2034.
------------------------------------
Resolution: Done
Done
> Inconsistent model naming validation in wizards and dialogs
> -----------------------------------------------------------
>
> Key: TEIIDDES-2034
> URL: https://issues.jboss.org/browse/TEIIDDES-2034
> Project: Teiid Designer
> …
[View More] Issue Type: Bug
> Affects Versions: 8.3, 8.3.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.4
>
>
> Performed an analysis of Designer's dialog and wizard panels validation of editable model names:
> 1) Refactor > Rename (*OK*)
> - Seems to allow only LETTERS, NUMBERS and '_' char
> - Shows appropriate error message
>
> 2) New Model Wizard (*FIX*)
> - Model name allows any char
>
> 3) Flat File and XML Import Wizards (*FIX*)
> - Source and View model names allow any char
> - View Table name only allows LETTERS, NUMBERS and '_' char
>
> 4) Import > WSDL File or URL >> Source and View Model (SOAP) (*FIX*)
> - Source and View model names allow any char
>
> 5) Import > WSDL File or URL >> Web Service Model (*FIX*)
> - Web Service Model Name allows any char (first page)
> - Schema model name allows any char (Workspace Location Selection page)
> - XML model name allows any char (last page)
>
> 6) JDBC Import wizard Model Name allows any char (*FIX*)
> 7) DDL Import Wizard (*OK*)
> - Appears to be working correctly: Allows only LETTERS, NUMBERS and '_' char
>
> 8) Import > Designer Test File >> Source or View Models (*FIX*)
> - Source and View model names allow any char
> - Utilizes Relational Model Selector dialog
> - Als used in "Create Materailized View Model" dialog
> 9) Create Web Service dialog (*FIX*)
> - schema and WS model names allow any char
>
> 10) Modeling > Create XML View Documents (*FIX*)
> - Select or create XML View model dialog allow any char for New Model Name
> - Similar to Relational Model Selector dialog
>
> 11) Import > Teiid Connection >> Source Model (*FIX*)
> - Source model name allows any char
--
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
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2034) Inconsistent model naming validation in wizards and dialogs
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2034?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2034:
-----------------------------------
Description:
Performed an analysis of Designer's dialog and wizard panels validation of editable model names:
1) Refactor > Rename (*OK*)
- Seems to allow only LETTERS, NUMBERS and '_' char
- Shows appropriate error message
2) New Model Wizard (*FIX*)
- Model name allows any char
3) Flat File and XML Import Wizards (*FIX*)
- …
[View More]Source and View model names allow any char
- View Table name only allows LETTERS, NUMBERS and '_' char
4) Import > WSDL File or URL >> Source and View Model (SOAP) (*FIX*)
- Source and View model names allow any char
5) Import > WSDL File or URL >> Web Service Model (*FIX*)
- Web Service Model Name allows any char (first page)
- Schema model name allows any char (Workspace Location Selection page)
- XML model name allows any char (last page)
6) JDBC Import wizard Model Name allows any char (*FIX*)
7) DDL Import Wizard (*OK*)
- Appears to be working correctly: Allows only LETTERS, NUMBERS and '_' char
8) Import > Designer Test File >> Source or View Models (*FIX*)
- Source and View model names allow any char
- Utilizes Relational Model Selector dialog
- Als used in "Create Materailized View Model" dialog
9) Create Web Service dialog (*FIX*)
- schema and WS model names allow any char
10) Modeling > Create XML View Documents (*FIX*)
- Select or create XML View model dialog allow any char for New Model Name
- Similar to Relational Model Selector dialog
11) Import > Teiid Connection >> Source Model (*FIX*)
- Source model name allows any char
was:
Performed an analysis of Designer's dialog and wizard panels validation of editable model names:
1) Refactor > Rename (*FIX*)
- Seems to allow only LETTERS, NUMBERS and '_' char
- error message only indicates "One or more characters are invalid" instead of more detailed message
2) New Model Wizard (*FIX*)
- Model name allows any char
3) Flat File and XML Import Wizards (*FIX*)
- Source and View model names allow any char
- View Table name only allows LETTERS, NUMBERS and '_' char
4) Import > WSDL File or URL >> Source and View Model (SOAP) (*FIX*)
- Source and View model names allow any char
5) Import > WSDL File or URL >> Web Service Model (*FIX*)
- Web Service Model Name allows any char (first page)
- Schema model name allows any char (Workspace Location Selection page)
- XML model name allows any char (last page)
6) JDBC Import wizard Model Name allows any char (*FIX*)
7) DDL Import Wizard (*OK*)
- Appears to be working correctly: Allows only LETTERS, NUMBERS and '_' char
8) Import > Designer Test File >> Source or View Models (*FIX*)
- Source and View model names allow any char
- Utilizes Relational Model Selector dialog
- Als used in "Create Materailized View Model" dialog
9) Create Web Service dialog (*FIX*)
- schema and WS model names allow any char
10) Modeling > Create XML View Documents (*FIX*)
- Select or create XML View model dialog allow any char for New Model Name
- Similar to Relational Model Selector dialog
11) Import > Teiid Connection >> Source Model (*FIX*)
- Source model name allows any char
> Inconsistent model naming validation in wizards and dialogs
> -----------------------------------------------------------
>
> Key: TEIIDDES-2034
> URL: https://issues.jboss.org/browse/TEIIDDES-2034
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3, 8.3.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.4
>
>
> Performed an analysis of Designer's dialog and wizard panels validation of editable model names:
> 1) Refactor > Rename (*OK*)
> - Seems to allow only LETTERS, NUMBERS and '_' char
> - Shows appropriate error message
>
> 2) New Model Wizard (*FIX*)
> - Model name allows any char
>
> 3) Flat File and XML Import Wizards (*FIX*)
> - Source and View model names allow any char
> - View Table name only allows LETTERS, NUMBERS and '_' char
>
> 4) Import > WSDL File or URL >> Source and View Model (SOAP) (*FIX*)
> - Source and View model names allow any char
>
> 5) Import > WSDL File or URL >> Web Service Model (*FIX*)
> - Web Service Model Name allows any char (first page)
> - Schema model name allows any char (Workspace Location Selection page)
> - XML model name allows any char (last page)
>
> 6) JDBC Import wizard Model Name allows any char (*FIX*)
> 7) DDL Import Wizard (*OK*)
> - Appears to be working correctly: Allows only LETTERS, NUMBERS and '_' char
>
> 8) Import > Designer Test File >> Source or View Models (*FIX*)
> - Source and View model names allow any char
> - Utilizes Relational Model Selector dialog
> - Als used in "Create Materailized View Model" dialog
> 9) Create Web Service dialog (*FIX*)
> - schema and WS model names allow any char
>
> 10) Modeling > Create XML View Documents (*FIX*)
> - Select or create XML View model dialog allow any char for New Model Name
> - Similar to Relational Model Selector dialog
>
> 11) Import > Teiid Connection >> Source Model (*FIX*)
> - Source model name allows any char
--
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
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-1982) Improve Error Dialog message for VDB deployment where source doesnt exist
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1982?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1982:
----------------------------------------
Played with this a bit... and debugged. The steps that the PreviewManager and ExecutionAdmin go through to get or create a data source do not provide a simple, clear-cut access point for just changing the method. Going to have to add more Status info up and down this framework to capture the "real" cause of "Can't Deploy".
…
[View More]
> Improve Error Dialog message for VDB deployment where source doesnt exist
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-1982
> URL: https://issues.jboss.org/browse/TEIIDDES-1982
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: VDB & Execution
> Affects Versions: 8.2
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Fix For: 8.4
>
> Attachments: ErrorDialog.png, MongoProjectSet.zip
>
>
> In some cases, when a user tries to deploy a VDB where one of the SourceModel DS does not exist, the user is prompted whether to create the source.
> I encountered a case though where an Error Dialog was displayed instead, with the message "No Connection Information in model xxx.xmi". For this case(Mongo) there is no CP available.
> Attaching model project set to reproduce, and a screen shot of the dialog.
> Message could be more informative, e.g. "The Data Source for model xxx.xmi cannot be found on server, and no CP information is available" or similar.
--
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
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2018:
----------------------------------------
After more digging, it appears the DDL importer isn't mapping datatypes based on string value key, so "integer" will map to "integer", etc..
The JDBC importer has a data type mapping class that offers more than just "find the built-in data type". Investigating more...
> DDL importer creates wrong data type …
[View More]for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
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
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2018:
----------------------------------------
Can you post all your builtin data type mappings you are using?
> DDL importer creates wrong data type for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> …
[View More]Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
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
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2018 at 1/28/14 11:50 AM:
------------------------------------------------------------------
It does seem odd/confusing. These built-in datatypes were defined a millenia ago. If we need to clean them up, seriously, feel free to make some recommendations.
1) As far as the Teiid DDL importer, we can catch this scenario rather easily and change all "integer" types to "xs:…
[View More]long".
2) We're setting the datatype to a numeric but not setting precision (default is 0) which results in a warning for each "numeric" column. What should the default be set to?
was (Author: blafond):
It does seem odd/confusing. These built-in datatypes were defined a millenia ago. If we need to clean them up, seriously, feel free to make some recommendations.
As far as the Teiid DDL importer, we can catch this scenario rather easily and change all "integer" types to "xs:long".
> DDL importer creates wrong data type for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
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
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2018:
----------------------------------------
It does seem odd/confusing. These built-in datatypes were defined a millenia ago. If we need to clean them up, seriously, feel free to make some recommendations.
As far as the Teiid DDL importer, we can catch this scenario rather easily and change all "integer" types to "xs:long".
> DDL importer creates wrong …
[View More]data type for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
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
[View Less]
11 years, 1 month