[JBoss JIRA] Moved: (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ]
Van Halbert moved JBDS-1687 to TEIIDDES-1010:
---------------------------------------------
Project: Teiid Designer (was: Developer Studio (JBoss Developer Studio))
Key: TEIIDDES-1010 (was: JBDS-1687)
Affects Version/s: 7.4
(was: 4.0.0.GA)
Component/s: Import/Export
(was: teiid)
> Indexes are not qualified when imported with Teiid Designer
> -----------------------------------------------------------
>
> Key: TEIIDDES-1010
> URL: https://issues.jboss.org/browse/TEIIDDES-1010
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.4
> Reporter: Marc Shirley
> Assignee: Barry LaFond
>
> Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-1002) Designer requires a more flexible Model Object Refactoring framework to handle pre and post transaction events.
by Barry LaFond (JIRA)
Designer requires a more flexible Model Object Refactoring framework to handle pre and post transaction events.
---------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1002
URL: https://issues.jboss.org/browse/TEIIDDES-1002
Project: Teiid Designer
Issue Type: Task
Components: Modeling, Validation
Affects Versions: 7.5
Reporter: Barry LaFond
Fix For: 7.5
The current modeling/editing event and transaction framework in Designer cannot satisfy the requirements to perform certain cross-metamodel clean-up.
In particular, if a user Deletes a Scalar Function, the ObjectDeleteCommand results in the dependent resources (i.e. Virtual Tables and Procedures) being re-validated, which is good, but the UDFManager doesn't have a chance to de-register the affected Function model before revalidation. The resulting validation is incorrect.
Because ObjectDeleteCommand is in designer.core, there isn't any direct way that command could tell the UDFManager to perform the library clean-up.
So I propose an to expand the current "refactorModelHandler" extension point to handle this processing.
The current "RefactorModelExtensionManager" should be renamed to "RefactorModelManager"
Methods should be added such as:
preProcess(int type, Object[] objects) (Where type = DELETE, RENAME, MOVE, ADD)
postProcess(int type, Object[] objects) (Where type = DELETE, RENAME, MOVE, ADD)
Objects could be be Models, Files or EObjects
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-228) Import transformation SQL fails to do anything
by Paul Nittel (JIRA)
Import transformation SQL fails to do anything
----------------------------------------------
Key: TEIIDDES-228
URL: https://jira.jboss.org/jira/browse/TEIIDDES-228
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.2.0
Environment: Fedora 10, Designer 20090922 build (same thing with RC1)
Reporter: Paul Nittel
I exported the transformation SQL from the VQT model. When I tried to import the SQL into a new VQT model, it gave the appearance it completed successfully, but none of the tables were defined. There were no errors or exceptions found in the log.
The format of the exported file is not the same as that of the Metadata Text Importer, so to use that route the file must be edited. (The export version takes into account the SELECT, INSERT, UPDATE, DELETE possibilities.) BTW, this had issues as well, but that's another JIRA.
--
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
12 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-181) Missing Java SQL Types In RelationalTypeMapping Interface And Implementation Class
by Dan Florian (JIRA)
Missing Java SQL Types In RelationalTypeMapping Interface And Implementation Class
----------------------------------------------------------------------------------
Key: TEIIDDES-181
URL: https://jira.jboss.org/jira/browse/TEIIDDES-181
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0
Reporter: Dan Florian
The following java.sql.Types constants do not have constants in RelationalTypeMapping or mappings in RelationalTypeMappingImpl: DATALINK, BOOLEAN, ROWID, LONGNVARCHAR, NCLOB, and SQLXML. All but the first 2 were added in JDK 1.6. Need to provide the mapping to the metamatrix datatypes for each or determine a mapping is not needed.
Also may want to look at using or referencing com.metamatrix.common.types.MMJDBCSQLTypeInfo instead of maintaining the mapping in two differenct classes.
See TEIIDDES-179 where NVARCHAR was added to fix this defect.
--
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
12 years, 11 months