[JBoss JIRA] Created: (TEIIDDES-550) Import DDL to Relational Table misses columns for primary, foreign keys
by Paul Nittel (JIRA)
Import DDL to Relational Table misses columns for primary, foreign keys
-----------------------------------------------------------------------
Key: TEIIDDES-550
URL: https://jira.jboss.org/browse/TEIIDDES-550
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1
Environment: Fedora 12, JBDS 3.0.1, TeiidDesigner 7.1 M1
Reporter: Paul Nittel
Attachments: motels.ddl
I imported the motels.ddl example file to populate the foo model. When finished importing, I had a number of errors where the importer had created primary and foreign keys without specifying columns for those keys. In one case, here's the DDL:
CREATE TABLE CustomerFamilyHistory
(
customerfamilyhistoryid number(10) CONSTRAINT customerfamilyhistoryid_pk PRIMARY KEY,
firstname varchar2(50) NOT NULL,
lastname varchar2(50) NOT NULL,
age number(3),
sibling varchar2(20),
customerid number(7) NOT NULL
);
The primary key, customerfamilyhistoryid_pk, is created, but no reference to customerfamilyhistoryid is provided.
--
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
13 years, 7 months
[JBoss JIRA] Created: (TEIIDDES-198) Error in TestServerRuntimeMetadata unit test
by Barry LaFond (JIRA)
Error in TestServerRuntimeMetadata unit test
--------------------------------------------
Key: TEIIDDES-198
URL: https://jira.jboss.org/jira/browse/TEIIDDES-198
Project: Teiid Designer
Issue Type: Bug
Reporter: Barry LaFond
Fix For: 6.1.1
Error in TestServerRuntimeMetadata.testGetXmlSchemas() method.
Appears that the TreeMappingRootSqlAspect.getTransformationInfo() method is calling toUpperCase() on the Import locations.
This results in an XSD file potentially having Case Sensitivity problems on LINUX, in this case.
Need to investigate removing this toUpperCase() call.
This has not manifested itself because it's a runtime/server thing and only happens if the XML validation is turned on which is basically not done. Our unit test happens to test ALL the basic methods and we haven't run unit tests consistently on LINUX until recently with Teiid Designer.
--
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
13 years, 8 months
[JBoss JIRA] Created: (TEIIDDES-482) Synchronizing models in a VDB does not work quite as expected
by Paul Nittel (JIRA)
Synchronizing models in a VDB does not work quite as expected
-------------------------------------------------------------
Key: TEIIDDES-482
URL: https://jira.jboss.org/browse/TEIIDDES-482
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.0
Environment: Fedora 12, OpenJDK, Designer from 6/28
Reporter: Paul Nittel
Attachments: SynchronizeThis.zip
Assuming I have a VDB which contains models,
1 - Modify one of the models
2 - Save the model
3 - The VDB editor shows the large "Synchronize All" button is enabled and the synch checkbox associated with the changed model is an empty checkbox. (The other checkboxes are large gray squares.)
4 - Click the checkbox (it now turns into the gray square - the large "All" button remains enabled)
5 - Save the VDB
Now the large "Synchronize All" button is disabled
If I click the "Synchronize All" button first, the checkbox is affected and the large button remains enabled until the VDB is saved. (If I click it again, it still goes through the synch process.)
I would expect the button and checkbox(es) to work together and that once all models are synched, the large button would be disabled even without the VDB being saved.
(Oddly, once I save a model in the VDB, the VDB becomes dirty. Maybe this is intentional, but now I don't have the option to deploy that VDB until I synch it.)
--
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
13 years, 8 months
[JBoss JIRA] Created: (TEIIDDES-609) Teiid QueryValidatorException opening VDB schema in Data Source Explorer for model with "hidden" table.
by Barry LaFond (JIRA)
Teiid QueryValidatorException opening VDB schema in Data Source Explorer for model with "hidden" table.
-------------------------------------------------------------------------------------------------------
Key: TEIIDDES-609
URL: https://jira.jboss.org/browse/TEIIDDES-609
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.1
Reporter: Barry LaFond
Assignee: John Doyle
Priority: Blocker
Fix For: 7.1.1
After creating a data role for PartsSupplier VDB where the CRUD for one table was turned OFF (i.e. create/read/update/delete = FALSE) and deploying to Teiid, I deployed and executed the VDB.
But on trying to view the contents in DTP, an exception occured.
org.teiid.jdbc.TeiidSQLException: Error trying to obtain schema metadata info on this connection: Remote org.teiid.api.exception.query.QueryValidatorException: User <Hcs7WsIzrd4G> is not entitled to action <Read> for 1 or more of the groups/elements/procedures..
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:102)
at org.teiid.jdbc.DatabaseMetaDataImpl.getSchemas(DatabaseMetaDataImpl.java:2361)
at org.teiid.jdbc.DatabaseMetaDataImpl.getSchemas(DatabaseMetaDataImpl.java:1298)
at org.eclipse.datatools.connectivity.sqm.loader.JDBCSchemaLoader.createResultSet(JDBCSchemaLoader.java:174)
at org.eclipse.datatools.connectivity.sqm.loader.JDBCSchemaLoader.loadSchemas(JDBCSchemaLoader.java:110)
at org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCCatalog.loadSchemas(JDBCCatalog.java:101)
at org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCCatalog.getSchemas(JDBCCatalog.java:64)
at org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.vnode.ServerExplorerVNodeContentProviderNav.displaySchemaNodeChildren(ServerExplorerVNodeContentProviderNav.java:126)
--
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
13 years, 8 months
[JBoss JIRA] Created: (TEIIDDES-644) Books example has incorrect transformation SQL in XML document model
by Paul Nittel (JIRA)
Books example has incorrect transformation SQL in XML document model
--------------------------------------------------------------------
Key: TEIIDDES-644
URL: https://jira.jboss.org/browse/TEIIDDES-644
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.1.1
Environment: JBDS 4.0.0 M2, Designer bulid H280
Reporter: Paul Nittel
Fix For: 7.1.1
I imported the Books Project into my workspace and found the XML document model had errors, Checking, I found the transformation SQL referenced the wrong models. For example,
SELECT
Books_Oracle.AUTHORS.LASTNAME AS author
FROM
Books_SQLServer.BOOK_AUTHORS, Books_Oracle.AUTHORS
WHERE
("input".isbn = Books_SQLServer.BOOK_AUTHORS.ISBN) AND (Books_SQLServer.BOOK_AUTHORS.AUTHOR_ID = Books_Oracle.AUTHORS.AUTHOR_ID)
should reference Books_SourceA and Books_SourceB rather than Books_SQLServer and Books_Oracle.
--
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
13 years, 8 months