May 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3469) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3469?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3469: ---------------------------------- Priority: Minor (was: Major) > Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator > ----------------------------------------------------------------------------------------------- > > Key: TEIID-3469 > URL: https://issues.jboss.org/browse/TEIID-3469 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Bruno Machado > Assignee: Steven Hawkins > Priority: Minor > Labels: ddl, designer, informix, schema, teiid > Fix For: 8.11 > > > When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'. > The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator. > useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3469) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3469?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-3469: ------------------------------------- Assignee: Steven Hawkins (was: Barry LaFond) > Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator > ----------------------------------------------------------------------------------------------- > > Key: TEIID-3469 > URL: https://issues.jboss.org/browse/TEIID-3469 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Bruno Machado > Assignee: Steven Hawkins > Labels: ddl, designer, informix, schema, teiid > Fix For: 8.11 > > > When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'. > The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator. > useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3469) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3469?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3469: ---------------------------------- Affects Version/s: 8.0 (was: 9.0) > Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator > ----------------------------------------------------------------------------------------------- > > Key: TEIID-3469 > URL: https://issues.jboss.org/browse/TEIID-3469 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Bruno Machado > Assignee: Steven Hawkins > Labels: ddl, designer, informix, schema, teiid > Fix For: 8.11 > > > When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'. > The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator. > useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3469) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3469?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3469: ---------------------------------- Fix Version/s: 8.11 > Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator > ----------------------------------------------------------------------------------------------- > > Key: TEIID-3469 > URL: https://issues.jboss.org/browse/TEIID-3469 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Bruno Machado > Assignee: Steven Hawkins > Labels: ddl, designer, informix, schema, teiid > Fix For: 8.11 > > > When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'. > The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator. > useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3469) Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-3469?page=com.atlassian.jira.plugin... ] Barry LaFond moved TEIIDDES-2498 to TEIID-3469: ----------------------------------------------- Project: Teiid (was: Teiid Designer) Key: TEIID-3469 (was: TEIIDDES-2498) Issue Type: Bug (was: Enhancement) Affects Version/s: 9.0 (was: 9.0) Workaround Description: Edit the NIS properties in the DDL by hand to replace the "." delimiters with ":" Component/s: (was: Import/Export) > Incorrect DDL Schema when importing from Teiid Data Source Connection using Informix translator > ----------------------------------------------------------------------------------------------- > > Key: TEIID-3469 > URL: https://issues.jboss.org/browse/TEIID-3469 > Project: Teiid > Issue Type: Bug > Affects Versions: 9.0 > Reporter: Bruno Machado > Assignee: Barry LaFond > Labels: ddl, designer, informix, schema, teiid > > When importing from Teiid Data Source Connection using an Informix Translator, an incorrect schema DDL is set as "catalog"."schema"."table-name" instead of "catalog":"schema"."table-name", the delimiter between catalog and schema is set to '.' but Informix uses ':'. > The '.' character must be replaced by a ':' between catalog and schema name when importing from Teiid Data Source Connection using Informix translator. > useCatalogName attribute could be set to false as a workaround to this and ignore the occurance of "catalog". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3467) expose bufferserviceimpl for configuration of buffermanager in embedded

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3467?page=com.atlassian.jira.plugin... ] Kylin Soong reassigned TEIID-3467: ---------------------------------- Assignee: Kylin Soong (was: Steven Hawkins) > expose bufferserviceimpl for configuration of buffermanager in embedded > ----------------------------------------------------------------------- > > Key: TEIID-3467 > URL: https://issues.jboss.org/browse/TEIID-3467 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Reporter: Steven Hawkins > Assignee: Kylin Soong > > We have a few configuration options exposed on the embeddedconfiguration related to the buffer manager, but should also look at exposing more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3039) Add support for odata expand

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3039 at 5/6/15 3:31 PM: --------------------------------------------------------------- {code} http://host/service/Customers?$expand=Orders($filter=$it/Address/City eq ShipTo/City) {code} becomes {code} customers left outer join orders on (customers.pkey = orders.fkey and (select city from address where address.fkey = customers.pkey) = (select city from shipTo where shipTo.pkey = orders.fkey)) {code} was (Author: rareddy): {code} http://host/service/Customers?$expand=Orders($filter=$it/Address/City eq ShipTo/City) {code} becomes {code} customers left outer join orders on (customers.pkey = orders.fkey and (select city from address where address.fkey = customers.pkey) = (select city from shipTo where shipTo.pkey = address.fkey)) {code} > Add support for odata expand > ---------------------------- > > Key: TEIID-3039 > URL: https://issues.jboss.org/browse/TEIID-3039 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Fix For: 8.12 > > > We should add support for odata expand. This can be done with logic similar to the xml document model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3039) Add support for odata expand

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-3039 at 5/6/15 3:29 PM: ------------------------------------------------------------- {code} http://host/service/Customers?$expand=Orders($filter=$it/Address/City eq ShipTo/City) {code} becomes {code} customers left outer join orders on (customers.pkey = orders.fkey and (select city from address where address.fkey = customers.pkey) = (select city from shipTo where shipTo.pkey = address.fkey)) {code} was (Author: rareddy): {code} http://host/service/Customers?$expand=Orders($filter=$it/Address/City eq ShipTo/City) {code} becomes {code} customers left outer join orders on (customers.pkey = orders.fkey and (select city from address where address.fkey = customers.pkey) = (select city from shipTo where shipTo.pkey = address.fkey)) {code} > Add support for odata expand > ---------------------------- > > Key: TEIID-3039 > URL: https://issues.jboss.org/browse/TEIID-3039 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Fix For: 8.12 > > > We should add support for odata expand. This can be done with logic similar to the xml document model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3039) Add support for odata expand

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3039: ------------------------------------- {code} http://host/service/Customers?$expand=Orders($filter=$it/Address/City eq ShipTo/City) {code} becomes {code} customers left outer join orders on (customers.pkey = orders.fkey and (select city from address where address.fkey = customers.pkey) = (select city from shipTo where shipTo.pkey = address.fkey)) {code} > Add support for odata expand > ---------------------------- > > Key: TEIID-3039 > URL: https://issues.jboss.org/browse/TEIID-3039 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Fix For: 8.12 > > > We should add support for odata expand. This can be done with logic similar to the xml document model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3468) Exception with same table name in materialization procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3468?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3468. ----------------------------------- Resolution: Done Updated the sysadmin sql and ensured there's escaping of the literals used in the materializationmanager. > Exception with same table name in materialization procedures > ------------------------------------------------------------ > > Key: TEIID-3468 > URL: https://issues.jboss.org/browse/TEIID-3468 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > The sql defining the mat view procedures is not qualifying the reference to the schemaName, and throwing an exception when the scalar subquery returns more than 1 value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2015