[JBoss JIRA] (TEIIDDES-2260) Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2260?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-2260:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1122470
> Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2260
> URL: https://issues.jboss.org/browse/TEIIDDES-2260
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: VDB & Execution
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Priority: Minor
>
> I don't know if it is a bug or there is some reason for that.
> When I create a condition for Data Role(& Save VDB) and then remove the condition(& Save VDB) Teiid Designer doesn't delete whole <permission> tag only the <condition> tag
> For example:
> Before removing
> <permission>
> <resource-name>Products_view.PRODUCTDATA</resource-name>
> <condition constraint="true">ISAMEXINT=1</condition>
> </permission>
> After removing:
> <permission>
> <resource-name>Products_view.PRODUCTDATA</resource-name>
> </permission>
> In my opinion Teiid Designer should delete whole <permission> tag and leave nothing behind..
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIIDDES-2260) Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2260?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2260:
-----------------------------------
Description:
I don't know if it is a bug or there is some reason for that.
When I create a condition for Data Role(& Save VDB) and then remove the condition(& Save VDB) Teiid Designer doesn't delete whole <permission> tag only the <condition> tag
For example:
Before removing
<permission>
<resource-name>Products_view.PRODUCTDATA</resource-name>
<condition constraint="true">ISAMEXINT=1</condition>
</permission>
After removing:
<permission>
<resource-name>Products_view.PRODUCTDATA</resource-name>
</permission>
In my opinion Teiid Designer should delete whole <permission> tag and leave nothing behind..
was:
I don't know if it is a bug or there is some reason for that.
When I create a condition for Data Role(& Save VDB) and then remove the condition(& Save VDB) Teiid Designer doesn't delete whole <permission> tag only the <condition> tag
For example:
Before removing
<permission>
<resource-name>Products_view.PRODUCTDATA</resource-name>
<condition constraint="true">ISAMEXINT=1</condition>
</permission>
After removing:
<permission>
<resource-name>Products_view.PRODUCTDATA</resource-name>
</permission>
I my opinion Teiid Designer should delete whole <permission> tag and leave nothing behind..
> Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2260
> URL: https://issues.jboss.org/browse/TEIIDDES-2260
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: VDB & Execution
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Priority: Minor
>
> I don't know if it is a bug or there is some reason for that.
> When I create a condition for Data Role(& Save VDB) and then remove the condition(& Save VDB) Teiid Designer doesn't delete whole <permission> tag only the <condition> tag
> For example:
> Before removing
> <permission>
> <resource-name>Products_view.PRODUCTDATA</resource-name>
> <condition constraint="true">ISAMEXINT=1</condition>
> </permission>
> After removing:
> <permission>
> <resource-name>Products_view.PRODUCTDATA</resource-name>
> </permission>
> In my opinion Teiid Designer should delete whole <permission> tag and leave nothing behind..
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIIDDES-2260) Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2260?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2260:
----------------------------------------
...it should delete the <permission> tag in case it has only <resource-name> tag in it
> Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2260
> URL: https://issues.jboss.org/browse/TEIIDDES-2260
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: VDB & Execution
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Priority: Minor
>
> I don't know if it is a bug or there is some reason for that.
> When I create a condition for Data Role(& Save VDB) and then remove the condition(& Save VDB) Teiid Designer doesn't delete whole <permission> tag only the <condition> tag
> For example:
> Before removing
> <permission>
> <resource-name>Products_view.PRODUCTDATA</resource-name>
> <condition constraint="true">ISAMEXINT=1</condition>
> </permission>
> After removing:
> <permission>
> <resource-name>Products_view.PRODUCTDATA</resource-name>
> </permission>
> In my opinion Teiid Designer should delete whole <permission> tag and leave nothing behind..
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIIDDES-2260) Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
by Matus Makovy (JIRA)
Matus Makovy created TEIIDDES-2260:
--------------------------------------
Summary: Teiid Designer doesn't clean up vdb.xml properly (Data Roles - conditions)
Key: TEIIDDES-2260
URL: https://issues.jboss.org/browse/TEIIDDES-2260
Project: Teiid Designer
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: VDB & Execution
Affects Versions: 8.3.3
Reporter: Matus Makovy
Priority: Minor
I don't know if it is a bug or there is some reason for that.
When I create a condition for Data Role(& Save VDB) and then remove the condition(& Save VDB) Teiid Designer doesn't delete whole <permission> tag only the <condition> tag
For example:
Before removing
<permission>
<resource-name>Products_view.PRODUCTDATA</resource-name>
<condition constraint="true">ISAMEXINT=1</condition>
</permission>
After removing:
<permission>
<resource-name>Products_view.PRODUCTDATA</resource-name>
</permission>
I my opinion Teiid Designer should delete whole <permission> tag and leave nothing behind..
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[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:
------------------------------------------
Teiid does not support a general default expression. As a hold over from MMX, we only support a string literal - https://docs.jboss.org/author/display/TEIID/BNF+for+SQL+Grammar#BNFforSQL...
> 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)
9 years, 10 months
[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:
----------------------------------------
If the CREATE TABLE statement defines the default as *DEFAULT 'c1'*, why are the paren's tic'd in the generated DDL? That seems like a bug?
I'm finding the BNF is commonly defined as *DEFAULT <expression>*. I've seen *DEFAULT someFunction()*, but I can't find any documentation that would allow ('c1').
> 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)
9 years, 10 months
[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 commented on TEIIDDES-2259:
----------------------------------------
There seem to be more ptroblems with this dialogue and checkboxes (screen1 attached)
> 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, screen1.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)
9 years, 10 months
[JBoss JIRA] (TEIIDDES-2259) Edit VDB Data Role dialogue doesn't check off checkboxes properly
by Matus Makovy (JIRA)
Matus Makovy created TEIIDDES-2259:
--------------------------------------
Summary: 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)
9 years, 10 months