[JBoss JIRA] (TEIIDDES-3217) Error reading Foreign Keys from Mysql 8.0
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3217?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-3217:
------------------------------------------
I can confirm that the import is successful on just the Teiid side, including the foreign key:
{code}
CREATE FOREIGN TABLE "IMS_db.ClientCompany" (
idClientCompany long NOT NULL AUTO_INCREMENT OPTIONS (ANNOTATION '', NAMEINSOURCE '`idClientCompany`', NATIVE_TYPE 'INT UNSIGNED'),
CompanyName string(255) NOT NULL OPTIONS (ANNOTATION '', NAMEINSOURCE '`CompanyName`', CHAR_OCTET_LENGTH 765, NATIVE_TYPE 'VARCHAR'),
Street string(255) NOT NULL OPTIONS (ANNOTATION '', NAMEINSOURCE '`Street`', CHAR_OCTET_LENGTH 765, NATIVE_TYPE 'VARCHAR'),
StreetNumber string(45) NOT NULL OPTIONS (ANNOTATION '', NAMEINSOURCE '`StreetNumber`', CHAR_OCTET_LENGTH 135, NATIVE_TYPE 'VARCHAR'),
CityCode string(45) NOT NULL OPTIONS (ANNOTATION '', NAMEINSOURCE '`CityCode`', CHAR_OCTET_LENGTH 135, NATIVE_TYPE 'VARCHAR'),
City string(255) NOT NULL OPTIONS (ANNOTATION '', NAMEINSOURCE '`City`', CHAR_OCTET_LENGTH 765, NATIVE_TYPE 'VARCHAR'),
fkCountry long NOT NULL OPTIONS (ANNOTATION '', NAMEINSOURCE '`fkCountry`', NATIVE_TYPE 'INT UNSIGNED'),
CONSTRAINT "PRIMARY" PRIMARY KEY(idClientCompany),
CONSTRAINT fkCountry FOREIGN KEY(fkCountry) REFERENCES IMS_db.Country (idCountry)
) OPTIONS (ANNOTATION '', NAMEINSOURCE '`IMS_db`.`ClientCompany`', UPDATABLE TRUE, "teiid_rel:fqn" 'catalog=IMS_db/table=ClientCompany', "teiid_rel:source_type" 'TABLE');
{code}
> Error reading Foreign Keys from Mysql 8.0
> -----------------------------------------
>
> Key: TEIIDDES-3217
> URL: https://issues.jboss.org/browse/TEIIDDES-3217
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 11.1.3
> Reporter: Christoph John
> Priority: Major
>
> I am currently trying to use TEIID designer together with a mysql 8.0 database to import a source model. Unfortunately, foreign keys cannot be read correctly. I assume it has to do with the VISIBLE flag on the index. Is there a known workaround available for mysql 8.0?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIIDDES-2954) Dynamic VDB doesn't contains apostrophe around procedure
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2954?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2954.
------------------------------------
Resolution: Out of Date
> Dynamic VDB doesn't contains apostrophe around procedure
> --------------------------------------------------------
>
> Key: TEIIDDES-2954
> URL: https://issues.jboss.org/browse/TEIIDDES-2954
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Major
> Attachments: completeJDGproject2.zip
>
>
> I have a project with JDG materialization. I have set
> After load script to: execute BookCacheSource.native('swap cache names');
> and
> Before load script to: execute BookCacheSource.native('truncate cache');
> When I generated Dynamic VDB and I want to deploy it, server shows me error that:
> {code:java}
> org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ", \"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT\" 'execute BookCacheSource.native('[*]swap[*] cache names" at line 10, column 188.
> Was expecting: "," | ")"
> {code}
> When I added another apostrophe to procedures in the DDL,
> execute BookCacheSource.native(''truncate cache'');
> execute BookCacheSource.native(''swap cache names'');
> deploy was successful.
> I think that DDL parser should add it automatically.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIIDDES-2963) Add Multi-selection capabilities on the directory tree
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2963?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2963:
----------------------------------------
[~dsteigne] I dug into this and I located where I could override the base class used for selection management in GEF, however, the complexity of the common pattern of selection with SHIFT key requires tracking the order of selection, or in particular, the "last" selected object (column in this case) if SHIFT key is down.
> Add Multi-selection capabilities on the directory tree
> ------------------------------------------------------
>
> Key: TEIIDDES-2963
> URL: https://issues.jboss.org/browse/TEIIDDES-2963
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.2.1
>
>
> When importing tables with a lot of columns, if the user wants to remove a bunch of columns, he needs to select them individually.
> Can the Designer have Multi-Selection capabilities, i.e. Shift or Control keys
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIIDDES-3020) Add new materialization properties
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3020?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3020:
-----------------------------------
Attachment: relational.mxd
> Add new materialization properties
> ----------------------------------
>
> Key: TEIIDDES-3020
> URL: https://issues.jboss.org/browse/TEIIDDES-3020
> Project: Teiid Designer
> Issue Type: Task
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Priority: Major
> Fix For: 12.0
>
> Attachments: relational.mxd
>
>
> In the teiid_rel namespace several new properties for materialized views have been added:
> MATVIEW_LOADNUMBER_COLUMN - references a column name on the materialization target table. Introduced with TEIID-4641 to offer more flexibility in refresh beyond swapping
> MATVIEW_WRITE_THROUGH - a boolean to denote whether updates against the view should also write into materialization target as well. Introduced with TEIID-3952
> There may be more related to the status table and debezium integration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIIDDES-3020) Add new materialization properties
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3020?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3020:
-----------------------------------
Fix Version/s: 12.0
> Add new materialization properties
> ----------------------------------
>
> Key: TEIIDDES-3020
> URL: https://issues.jboss.org/browse/TEIIDDES-3020
> Project: Teiid Designer
> Issue Type: Task
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Priority: Major
> Fix For: 12.0
>
>
> In the teiid_rel namespace several new properties for materialized views have been added:
> MATVIEW_LOADNUMBER_COLUMN - references a column name on the materialization target table. Introduced with TEIID-4641 to offer more flexibility in refresh beyond swapping
> MATVIEW_WRITE_THROUGH - a boolean to denote whether updates against the view should also write into materialization target as well. Introduced with TEIID-3952
> There may be more related to the status table and debezium integration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month
[JBoss JIRA] (TEIIDDES-3020) Add new materialization properties
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3020?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3020:
-----------------------------------
Fix Version/s: (was: 11.2.1)
> Add new materialization properties
> ----------------------------------
>
> Key: TEIIDDES-3020
> URL: https://issues.jboss.org/browse/TEIIDDES-3020
> Project: Teiid Designer
> Issue Type: Task
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Priority: Major
> Fix For: 12.0
>
>
> In the teiid_rel namespace several new properties for materialized views have been added:
> MATVIEW_LOADNUMBER_COLUMN - references a column name on the materialization target table. Introduced with TEIID-4641 to offer more flexibility in refresh beyond swapping
> MATVIEW_WRITE_THROUGH - a boolean to denote whether updates against the view should also write into materialization target as well. Introduced with TEIID-3952
> There may be more related to the status table and debezium integration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 1 month