Bug 1166248
| Summary: | Inconsistent column datatypes when importing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Andrej Smigala <asmigala> | ||||
| Component: | Tooling | Assignee: | Barry LaFond <blafond> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.0 | CC: | anmahaja, atangrin, mmakovy, vhalbert | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
When you import datatypes using the JDBC Impoter, you may observe multiple discrepancies in the column datatypes.
This behaviour persists in JBoss Data Virtualization 6.1.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-02-05 08:29:15 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Plan is to work TEIIDDES-2398 for Designer 9.1 and 8.6.2 patch release. The design would insert an extra page on the importers (JDBC & Teiid Connection) that displays the datatype mappings that will be used by default. User can then switch/change any of the datatype mappings before the model is actually constructed at the end of the import. Should be able to utilize the same page in both importers. Closing this since we are tracking issues for tooling only in JIRA from now on. Barry LaFond <blafond> updated the status of jira TEIIDDES-2398 to Resolved |
Created attachment 959438 [details] datatypes There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer. Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle)