March 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2460: ---------------------------------------------- Bugzilla Update: (was: Perform) > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Fix For: 9.1, 9.0.2 > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2460: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1193562 > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Fix For: 9.1, 9.0.2 > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2460: -------------------------------------- Assignee: Mark Drilling > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2 > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2460: -------------------------------------- Summary: JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB Key: TEIIDDES-2460 URL: https://issues.jboss.org/browse/TEIIDDES-2460 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Barry LaFond Fix For: 9.1, 9.0.2 When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised Version-Release number of selected component (if applicable): Actual results: Imported schema has changed integer data type to biginteger data type. Expected results: Imported schema will be identical to original schema. Additional info: Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2434) Renaming issues - with folders inside project

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2434?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2434: ----------------------------------- Fix Version/s: 9.1 9.0.2 > Renaming issues - with folders inside project > --------------------------------------------- > > Key: TEIIDDES-2434 > URL: https://issues.jboss.org/browse/TEIIDDES-2434 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: Windows > Reporter: Matus Makovy > Assignee: Paul Richardson > Fix For: 9.1, 9.0.2 > > > More issues with renaming models. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2434) Renaming issues - with folders inside project

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2434?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2434: -------------------------------------- Assignee: Paul Richardson > Renaming issues - with folders inside project > --------------------------------------------- > > Key: TEIIDDES-2434 > URL: https://issues.jboss.org/browse/TEIIDDES-2434 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: Windows > Reporter: Matus Makovy > Assignee: Paul Richardson > > More issues with renaming models. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2297) I can't see whole model editor buttons on Fedora, they are cropped.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2297?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2297: ----------------------------------- Fix Version/s: 9.2 (was: 9.1) > I can't see whole model editor buttons on Fedora, they are cropped. > ------------------------------------------------------------------- > > Key: TEIIDDES-2297 > URL: https://issues.jboss.org/browse/TEIIDDES-2297 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 8.3.3 > Environment: Fedora 20 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Minor > Fix For: 9.2 > > Attachments: screen.png > > > Model editor buttons are cropped. [screenshot] On Windows 7 they are OK, only on Linux (I have Fedora 20) user can't see whole buttons. > User doesn't have the option to expand the panel on the left side to see whole buttons. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2248) Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2248: ----------------------------------- Fix Version/s: 9.2 > Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2248 > URL: https://issues.jboss.org/browse/TEIIDDES-2248 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Affects Versions: 8.3.3 > Environment: Teiid Designer 8.3.3 > Teiid 8.4.1-redhat-7 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2 > > Attachments: screen-1.png > > > Create a table with > {code:sql} > CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' ) > {code} > When trying to import it through Teiid Connection Importer, the importer DDL is shown as > {code:sql} > CREATE FOREIGN TABLE "dballo00.dbo.t1" ( > c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar') > ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0); > {code} > but on the next page, the following error is shown (see screenshot): > The DDL failed to parse with message: "Unparsable table body". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2248) Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2248: ---------------------------------------- This appears to be a MS Teiid Parsing issue. The work-around is to save the DDL to your filesystem/workspace, remove the offending quotes and re-import using the DDL Importer selecting the Teiid Dialect. Going to clone this and move to Modeshape JIRA > Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2248 > URL: https://issues.jboss.org/browse/TEIIDDES-2248 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Affects Versions: 8.3.3 > Environment: Teiid Designer 8.3.3 > Teiid 8.4.1-redhat-7 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2 > > Attachments: screen-1.png > > > Create a table with > {code:sql} > CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' ) > {code} > When trying to import it through Teiid Connection Importer, the importer DDL is shown as > {code:sql} > CREATE FOREIGN TABLE "dballo00.dbo.t1" ( > c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar') > ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0); > {code} > but on the next page, the following error is shown (see screenshot): > The DDL failed to parse with message: "Unparsable table body". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2422: -------------------------------------- Assignee: Ted Jones > XSD model created in wrong folder when creating Web service model from WSDL > --------------------------------------------------------------------------- > > Key: TEIIDDES-2422 > URL: https://issues.jboss.org/browse/TEIIDDES-2422 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Andrej Šmigala > Assignee: Ted Jones > Priority: Minor > Fix For: 9.1, 9.0.2 > > > When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder. > Expected result: > The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder. > Actual result: > The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2015