January 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2760) built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2760?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2760: ----------------------------------- Component/s: Patch Release > built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2760 > URL: https://issues.jboss.org/browse/TEIIDDES-2760 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Teiid Integration > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.0.5, 9.2.1 > > > When base64Binary built in type was added to BuiltinDatatypes.xsd, the runtime type was mistakenly set to type "string" rather than varbinary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2751) Add ability to import Oracle Packages via JDBC Import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2751?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2751: ----------------------------------- Priority: Blocker (was: Major) > Add ability to import Oracle Packages via JDBC Import > ----------------------------------------------------- > > Key: TEIIDDES-2751 > URL: https://issues.jboss.org/browse/TEIIDDES-2751 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Patch Release > Affects Versions: 9.0.2 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.2.1 > > > When using the JDBC importer with an Oracle datasource, Oracle Packages are not available to be selected. I am only allowed to select Tables, Views, and Procedures. There should be an option to select Packages, which in my case contains stored procedures. > A ticket was submitted on the TEIID side to support this functionality. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2754) Extracting models from VDB without Quick Fix?

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2754?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2754: ----------------------------------- Attachment: QT_MySql50_Push.vdb > Extracting models from VDB without Quick Fix? > --------------------------------------------- > > Key: TEIIDDES-2754 > URL: https://issues.jboss.org/browse/TEIIDDES-2754 > Project: Teiid Designer > Issue Type: Enhancement > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Attachments: QT_MySql50_Push.vdb, Screen Shot 2016-01-12 at 9.44.44 (2).png > > > I am testing backwards compatibility with VDBs generated from older versions of TD. I imported finished VDB and I am trying to deploy it to my server. > First thing I came across: > Is there a way to extract models from VDB except the Quick fix? I haven't found any other option. > If there is not, I'd suggest to include such option in context menu after right-clicking the VDB. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2756) After importing older models transformation SQL is missing "AS columnName" part

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2756?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2756: ----------------------------------- Attachment: QT_MySql50_Push.vdb > After importing older models transformation SQL is missing "AS columnName" part > ------------------------------------------------------------------------------- > > Key: TEIIDDES-2756 > URL: https://issues.jboss.org/browse/TEIIDDES-2756 > Project: Teiid Designer > Issue Type: Enhancement > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Attachments: QT_MySql50_Push.vdb, Screen Shot 2016-01-12 at 10.30.21 (2).png, Screen Shot 2016-01-12 at 10.30.37 (2).png > > > After I imported some older VDB and exported models from this VDB, there seem to be some validation errors. > It is necessary to add "AS ColumnName" to transformation sql. > See screenshots > Is there a possibility that TD would do this automatically? Or could we have at least some Quick fix for this? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2746) Dynamic VDB export and import set bigdecimal precision to 20 if not defined and should be 0

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2746?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2746 at 1/12/16 4:59 PM: ----------------------------------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/8d37e5cb4726edc31... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/cac539fd772582b93... was (Author: blafond): master: https://github.com/Teiid-Designer/teiid-designer/commit/8d37e5cb4726edc31... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/8d37e5cb4726edc31... > Dynamic VDB export and import set bigdecimal precision to 20 if not defined and should be 0 > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2746 > URL: https://issues.jboss.org/browse/TEIIDDES-2746 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Patch Release > Affects Versions: 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 9.0.5, 9.2.1 > > > Import vdb-xml into Teiid vdb: attribute with bigdecimal type (without precision) gets converted into bigdecimal(20) type (with precision=20), expected bigdecimal type > and > Export teiid-vdb to vdb-xml: attribute with bigdecimal type (without precision) gets converted into bigdecimal(20) type (with precision=20), expected bigdecimal type > If no precision is specified default to 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2760) built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2760?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2760 at 1/12/16 3:56 PM: ----------------------------------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/bf88579ea0e5654c8... 9.0.x was (Author: blafond): master: https://github.com/Teiid-Designer/teiid-designer/commit/bf88579ea0e5654c8... > built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2760 > URL: https://issues.jboss.org/browse/TEIIDDES-2760 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.0.5, 9.2.1 > > > When base64Binary built in type was added to BuiltinDatatypes.xsd, the runtime type was mistakenly set to type "string" rather than varbinary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2760) built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2760?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2760: ----------------------------------- Fix Version/s: 9.0.5 > built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2760 > URL: https://issues.jboss.org/browse/TEIIDDES-2760 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.0.5, 9.2.1 > > > When base64Binary built in type was added to BuiltinDatatypes.xsd, the runtime type was mistakenly set to type "string" rather than varbinary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2760) built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2760?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2760. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/bf88579ea0e5654c8... > built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2760 > URL: https://issues.jboss.org/browse/TEIIDDES-2760 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.0.5, 9.2.1 > > > When base64Binary built in type was added to BuiltinDatatypes.xsd, the runtime type was mistakenly set to type "string" rather than varbinary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2760) built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2760: -------------------------------------- Summary: built-in varbinary datatype needs to be defined as a varbinary runtime type rather than string Key: TEIIDDES-2760 URL: https://issues.jboss.org/browse/TEIIDDES-2760 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 9.2.1 When base64Binary built in type was added to BuiltinDatatypes.xsd, the runtime type was mistakenly set to type "string" rather than varbinary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2756) After importing older models transformation SQL is missing "AS columnName" part

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2756?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2756: ---------------------------------------- [~mmakovy] Can you attach the VDB you tested with? and to the related new jiras as well? > After importing older models transformation SQL is missing "AS columnName" part > ------------------------------------------------------------------------------- > > Key: TEIIDDES-2756 > URL: https://issues.jboss.org/browse/TEIIDDES-2756 > Project: Teiid Designer > Issue Type: Enhancement > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Attachments: Screen Shot 2016-01-12 at 10.30.21 (2).png, Screen Shot 2016-01-12 at 10.30.37 (2).png > > > After I imported some older VDB and exported models from this VDB, there seem to be some validation errors. > It is necessary to add "AS ColumnName" to transformation sql. > See screenshots > Is there a possibility that TD would do this automatically? Or could we have at least some Quick fix for this? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2016