[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2018:
------------------------------------------
> Q: Should the Teiid Import option look at native type (i.e. int) and use that instead? or map integer >> int
I'm not sure what you mean. We need to be consistent here with there the type names come from. From a teiid/sql perspective int/integer are just synonyms. So I'm not sure by what you mean by map integer to int, double to float, etc. You have to say what domain each of the terms apply to. From there we can say things like teiid double = sql server float, xsd integer = teiid biginteger, and so on and so forth.
Generally the DDL importer when importing Teiid DDL should always use the Teiid type as the runtime type. The native type is not necessary in making the determination.
> 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
>
> Attachments: types_comparison.png
>
>
> 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
10 years, 3 months
[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/29/14 4:33 PM:
-----------------------------------------------------------------
So let's walk through a couple scenarios...
1) column named *type_int* of type *int*
* JDBC import
** converts to type *int*
* Teiid DDL contains type = *integer* and native type = *integer*
** converts to type *integer*
Q: Should the Teiid Import option look at native type (i.e. *int*) and use that instead? or map *integer* >> *int*
2) column named *type_float*
* JDBC import
** converts to type *float*
* Teiid DDL contains type = *double* and native type = *float*
** converts to type *double*
Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float*
3) column named *type_character_10*
* JDBC import
** converts to type *char(10)*
* Teiid DDL contains type = *string(10)* and native type = *char*
** converts to type *string(10*
Q: Should the Teiid Import option look at native type (i.e. *char*) and use that instead? Based on *string(10)* there no way to tell that this is a *char(10)* without looking at the native type
was (Author: blafond):
So let's walk through a couple scenarios...
1) column named *type_int* of type *int*
* JDBC import
** converts to type *int*
* Teiid DDL contains type = *integer* and native type = *integer*
** converts to type *integer*
Q: Should the Teiid Import option look at native type (i.e. *int*) and use that instead? or map *integer* >> *int*
2) column named *type_float*
* JDBC import
** converts to type *float*
* Teiid DDL contains type = *double* and native type = *float*
** converts to type *double*
Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float*
> 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
>
> Attachments: types_comparison.png
>
>
> 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
10 years, 3 months
[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/29/14 4:30 PM:
-----------------------------------------------------------------
So let's walk through a couple scenarios...
1) column named *type_int* of type *int*
* JDBC import
** converts to type *int*
* Teiid DDL contains type = *integer* and native type = *integer*
** converts to type *integer*
Q: Should the Teiid Import option look at native type (i.e. *int*) and use that instead? or map *integer* >> *int*
2) column named *type_float*
* JDBC import
** converts to type *float*
* Teiid DDL contains type = *double* and native type = *float*
** converts to type *double*
Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float*
was (Author: blafond):
So let's walk through a couple scenarios...
1) column named *type_int* of type *int*
* JDBC import >> converts to type *int*
* Teiid DDL contains type = *integer* and native type = *integer*
** converts to type *integer*
Q: Should the Teiid Import option look at native type (i.e. *int*) and use that instead? or map *integer* >> *int*
2) column named *type_float*
* JDBC import >> converts to type *float*
* Teiid DDL contains type = *double* and native type = *float*
** converts to type *double*
Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float*
> 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
>
> Attachments: types_comparison.png
>
>
> 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
10 years, 3 months
[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/29/14 4:29 PM:
-----------------------------------------------------------------
So let's walk through a couple scenarios...
1) column named *type_int* of type *int*
* JDBC import >> converts to type *int*
* Teiid DDL contains type = *integer* and native type = *integer*
** converts to type *integer*
Q: Should the Teiid Import option look at native type (i.e. *int*) and use that instead? or map *integer* >> *int*
2) column named *type_float*
* JDBC import >> converts to type *float*
* Teiid DDL contains type = *double* and native type = *float*
** converts to type *double*
Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float*
was (Author: blafond):
So let's walk through a couple scenarios...
1) column named *type_int* of type *int*
* JDBC import >> converts to type *int*
* Teiid DDL contains type = *integer* and native type = *integer*
Q: Should the Teiid Import option look at native type (i.e. *int*) and use that instead? or map *integer* >> *int*
2) column named *type_float*
* JDBC import >> converts to type *float*
* Teiid DDL contains type = *double* and native type = *float*
Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float*
> 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
>
> Attachments: types_comparison.png
>
>
> 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
10 years, 3 months
[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:
----------------------------------------
So let's walk through a couple scenarios...
1) column named *type_int* of type *int*
* JDBC import >> converts to type *int*
* Teiid DDL contains type = *integer* and native type = *integer*
Q: Should the Teiid Import option look at native type (i.e. *int*) and use that instead? or map *integer* >> *int*
2) column named *type_float*
* JDBC import >> converts to type *float*
* Teiid DDL contains type = *double* and native type = *float*
Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float*
> 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
>
> Attachments: types_comparison.png
>
>
> 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
10 years, 3 months
[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:
----------------------------------------
In the image:
* ALL_TYPES_JDBC is imported via JDBC importer
* ALL_TYPES_TEIID is imported via Teiid Connection Importer which operates on the above DDL during that import.
We do not currently map the DDL column datatypes in the Teiid Connection importer. Hence, "integer" results in the built-in-type "integer".
So what should the mappings be? And is our JDBC importer mapping types correctl?
> 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
>
> Attachments: types_comparison.png
>
>
> 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
10 years, 3 months
[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 updated TEIIDDES-2018:
-----------------------------------
Attachment: types_comparison.png
> 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
>
> Attachments: types_comparison.png
>
>
> 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
10 years, 3 months
[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 updated TEIIDDES-2018:
-----------------------------------
Attachment: (was: types_comparison.xcf)
> 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
>
> Attachments: types_comparison.png
>
>
> 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
10 years, 3 months
[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:
----------------------------------------
So here ALL_TYPES_JDBC is imported from SQLServer
and ALL_TYPES_TEIID is import of DDL of previous? And the DDL is shown above?
I believe the error is in the DDL parsing or built-in-type mapping there is wrong mapping.
> 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
>
> Attachments: types_comparison.xcf
>
>
> 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
10 years, 3 months
[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 updated TEIIDDES-2018:
-----------------------------------
Attachment: types_comparison.xcf
> 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
>
> Attachments: types_comparison.xcf
>
>
> 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
10 years, 3 months