July 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2259) Edit VDB Data Role dialogue doesn't check off checkboxes properly

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2259?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2259: ----------------------------------- Attachment: screen.png screenshot > Edit VDB Data Role dialogue doesn't check off checkboxes properly > ----------------------------------------------------------------- > > Key: TEIIDDES-2259 > URL: https://issues.jboss.org/browse/TEIIDDES-2259 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.3 > Reporter: Matus Makovy > Attachments: screen.png > > > When I tick, for example, "Create" on one column and "Read" on the same column and then check off "Create", the gray checkboxes stay the same. Only after I check off "Read" on this column all disappear... screenshot attached > JBDS 7.1.1.GA + Teiid Designer 8.3.3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2248: ------------------------------------------ '(''c1'')' is a valid string. You need to see what the parser error actually is. > 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 > Security Level: Public(Everyone can see) > 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 > 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.2.6#6264)

11 years, 3 months

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 edited comment on TEIIDDES-2248 at 7/21/14 2:47 PM: ----------------------------------------------------------------- The parser works if the '' are removed from the parens {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} is '(''c1'')' valid syntax? was (Author: blafond): The parser works if the '' are removed from the parens {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} > 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 > Security Level: Public(Everyone can see) > 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 > 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.2.6#6264)

11 years, 3 months

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: ---------------------------------------- The parser works if the '' are removed from the parens {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} > 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 > Security Level: Public(Everyone can see) > 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 > 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.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2257) Create VDB DataSource Dialog Enhancements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2257?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2257: ---------------------------------------- not one more pop up -:( > Create VDB DataSource Dialog Enhancements > ----------------------------------------- > > Key: TEIIDDES-2257 > URL: https://issues.jboss.org/browse/TEIIDDES-2257 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Usability > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > Attachments: create-vdb-data-source-in-server-view.png, ds.png, vdb-datasource-exists-dialog.png > > > 1) The dialog shows "OK" and "Cancel" buttons, they need to be "yes" or "no" buttons. > 2) If the data source is already available in server, then do not ask the user if they want to create it again. > Even better is, ask on the vdb-explorer window to enter (pre-fill) the JNDI name, with a check-box to create or not, rather than asking at later time. No annoying pop-up dialog. > Plus Points: To be useful, provide right click on VDB in server panel and create a Data source. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2257) Create VDB DataSource Dialog Enhancements

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2257?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2257. ------------------------------------ Resolution: Done Fixed in master and 8.5.x > Create VDB DataSource Dialog Enhancements > ----------------------------------------- > > Key: TEIIDDES-2257 > URL: https://issues.jboss.org/browse/TEIIDDES-2257 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Usability > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > Attachments: create-vdb-data-source-in-server-view.png, ds.png, vdb-datasource-exists-dialog.png > > > 1) The dialog shows "OK" and "Cancel" buttons, they need to be "yes" or "no" buttons. > 2) If the data source is already available in server, then do not ask the user if they want to create it again. > Even better is, ask on the vdb-explorer window to enter (pre-fill) the JNDI name, with a check-box to create or not, rather than asking at later time. No annoying pop-up dialog. > Plus Points: To be useful, provide right click on VDB in server panel and create a Data source. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2257) Create VDB DataSource Dialog Enhancements

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2257?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2257: ----------------------------------- Attachment: vdb-datasource-exists-dialog.png > Create VDB DataSource Dialog Enhancements > ----------------------------------------- > > Key: TEIIDDES-2257 > URL: https://issues.jboss.org/browse/TEIIDDES-2257 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Usability > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > Attachments: create-vdb-data-source-in-server-view.png, ds.png, vdb-datasource-exists-dialog.png > > > 1) The dialog shows "OK" and "Cancel" buttons, they need to be "yes" or "no" buttons. > 2) If the data source is already available in server, then do not ask the user if they want to create it again. > Even better is, ask on the vdb-explorer window to enter (pre-fill) the JNDI name, with a check-box to create or not, rather than asking at later time. No annoying pop-up dialog. > Plus Points: To be useful, provide right click on VDB in server panel and create a Data source. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2256 at 7/21/14 12:28 PM: ------------------------------------------------------------------ Teiid Runtime Types {code} enum DataTypeName { STRING, BOOLEAN, BYTE, SHORT, CHAR, INTEGER, LONG, BIG_INTEGER, FLOAT, DOUBLE, BIG_DECIMAL, DATE, TIME, TIMESTAMP, OBJECT, NULL, BLOB, CLOB, XML, VARCHAR, TINYINT, SMALLINT, BIGINT, REAL, DECIMAL, @Since(Version.TEIID_8_0) VARBINARY } {code} was (Author: blafond): enum DataTypeName { STRING, BOOLEAN, BYTE, SHORT, CHAR, INTEGER, LONG, BIG_INTEGER, FLOAT, DOUBLE, BIG_DECIMAL, DATE, TIME, TIMESTAMP, OBJECT, NULL, BLOB, CLOB, XML, VARCHAR, TINYINT, SMALLINT, BIGINT, REAL, DECIMAL, @Since(Version.TEIID_8_0) VARBINARY } > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > Attachments: full-datatypes-1.png, full-datatypes-2.png > > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2256: ----------------------------------- Attachment: full-datatypes-1.png full-datatypes-2.png enum DataTypeName { STRING, BOOLEAN, BYTE, SHORT, CHAR, INTEGER, LONG, BIG_INTEGER, FLOAT, DOUBLE, BIG_DECIMAL, DATE, TIME, TIMESTAMP, OBJECT, NULL, BLOB, CLOB, XML, VARCHAR, TINYINT, SMALLINT, BIGINT, REAL, DECIMAL, @Since(Version.TEIID_8_0) VARBINARY } > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > Attachments: full-datatypes-1.png, full-datatypes-2.png > > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2252) Add preference to importers to specify which characters should be substituted for

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2252?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2252: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1048948|https://bugzilla.redhat.com/show_bug.cgi?id=1048948] from MODIFIED to ASSIGNED > Add preference to importers to specify which characters should be substituted for > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2252 > URL: https://issues.jboss.org/browse/TEIIDDES-2252 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.5 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.6 > > > Add a preference that would allow the user to specify a set of characters that should be replaced by another character. > This enhancement will resolve the issue when ModeShape metadata is being imported using the Teiid Connection importer, and will allow the user to substitute the colon for an underscore. But would also be available for any other data source that would have need for this type of substitution. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2014