[
https://jira.jboss.org/jira/browse/TEIIDDES-217?page=com.atlassian.jira.p...
]
Mark Drilling commented on TEIIDDES-217:
----------------------------------------
I have uploaded the patch I applied to RelationalModelProcessorImpl in previous versions.
Barry and I discussed a different approach for consideration and inclusion in teiid. The
alternate approach involved creating a new extension point in the c.m.modeler.jdbc plugin.
The extension point would allow custom processing for the different db types similar to
what is currently done in c.m.modeler.jdbc.relational plugin. The 'addResults'
method in the Response object would need custom override based on the database type. The
ResultSet object could be intercepted and modified if necessary in that method. This
would fix the display issue we were seeing in the import wizard table as well. I have
attached the code change patch for consideration in the next release.
JDBC Import Error from MySQL with BIT datatypes
-----------------------------------------------
Key: TEIIDDES-217
URL:
https://jira.jboss.org/jira/browse/TEIIDDES-217
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0, 6.1.0, 6.2.0, Future
Reporter: Mark Drilling
Assignee: Barry LaFond
Priority: Minor
Attachments: CVSPATCH-RelationalModelProcessorImpl.txt
JDBC import from a MySQL database having columns of BIT datatype fails.
The import succeeds, but attempts to re-open the generated relational model fail. Further
inspection of the .xmi shows that an incorrect 'defaultValue' for the column has
been written to the xmi model file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira