[
https://jira.jboss.org/browse/TEIID-1149?page=com.atlassian.jira.plugin.s...
]
Steve Hawkins commented on TEIID-1149:
--------------------------------------
This is due to the use of the model based indexes. Previously each set of indexes
included a copy of the datatype information. Now only the system metadata has a datatype
index. We can do a couple of things. The logic to produce the columns table information
could be made tolerant of not having a datatype reference (currently it just skips the
record, which was the old behavior and limited to a corner case with mapping class
columns). We can pass in the built in type information during the load of the model based
indexes so that the datatype uuid references get properly resolved.
If Designer does not want to keep reindexing the built-in datatypes, that would be fine -
but it still needs to index new enterprise types.
Importing tables from a deployed VDB does not import columns
------------------------------------------------------------
Key: TEIID-1149
URL:
https://jira.jboss.org/browse/TEIID-1149
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.0
Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final
Reporter: Paul Nittel
Attachments: NoColumns.png, TeiidDes-506Projects.zip
I created, and deployed, a VDB containing source and view models. I am able to query
these tables.
I created a new project and into that project I attempted to import a view model's
table from the previously-created VDB. What I found in the imported was the models and
tables were shown, but no columns were available for import. Once imported, the tables did
have no columns.
Screenshot and other stuff attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira