April 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4849) Google translator behaves unexpectedly with Double in WHERE clause of SELECT

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIID-4849?page=com.atlassian.jira.plugin... ] Lucie Fabrikova updated TEIID-4849: ----------------------------------- Issue Type: Feature Request (was: Bug) > Google translator behaves unexpectedly with Double in WHERE clause of SELECT > ---------------------------------------------------------------------------- > > Key: TEIID-4849 > URL: https://issues.jboss.org/browse/TEIID-4849 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > > Query like "SELECT DoubleNum FROM SmallA WHERE DoubleNum > 5.0" gives unexpected results for following values in DoubleNum column: > * value like '15.1' is probably by google spreadsheet interpreted as date (in function row in sheet appears 15.1.2017), SELECT query returns no results > * value like '150.1': SELECT returns null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4849) Google translator behaves unexpectedly with Double in WHERE clause of SELECT

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIID-4849?page=com.atlassian.jira.plugin... ] Lucie Fabrikova updated TEIID-4849: ----------------------------------- Priority: Minor (was: Major) > Google translator behaves unexpectedly with Double in WHERE clause of SELECT > ---------------------------------------------------------------------------- > > Key: TEIID-4849 > URL: https://issues.jboss.org/browse/TEIID-4849 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Priority: Minor > > Query like "SELECT DoubleNum FROM SmallA WHERE DoubleNum > 5.0" gives unexpected results for following values in DoubleNum column: > * value like '15.1' is probably by google spreadsheet interpreted as date (in function row in sheet appears 15.1.2017), SELECT query returns no results > * value like '150.1': SELECT returns null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4849) Google translator behaves unexpectedly with Double in WHERE clause of SELECT

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIID-4849?page=com.atlassian.jira.plugin... ] Lucie Fabrikova reopened TEIID-4849: ------------------------------------ It might be useful to enable easier communication with other locales of Google Sheets - setting to Feature Request. > Google translator behaves unexpectedly with Double in WHERE clause of SELECT > ---------------------------------------------------------------------------- > > Key: TEIID-4849 > URL: https://issues.jboss.org/browse/TEIID-4849 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > > Query like "SELECT DoubleNum FROM SmallA WHERE DoubleNum > 5.0" gives unexpected results for following values in DoubleNum column: > * value like '15.1' is probably by google spreadsheet interpreted as date (in function row in sheet appears 15.1.2017), SELECT query returns no results > * value like '150.1': SELECT returns null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4852) Wrong OData results with multiple self relationships

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4852?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4852. ----------------------------------- Resolution: Done Changed the logic to use the navigation property when determining the foreign key to follow. > Wrong OData results with multiple self relationships > ---------------------------------------------------- > > Key: TEIID-4852 > URL: https://issues.jboss.org/browse/TEIID-4852 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.3, 9.1.5, 9.2.2 > > > If an entity has multiple self relationships, only the first foreign key will be used no matter which navigation is queried. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4852) Wrong OData results with multiple self relationships

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4852: ------------------------------------- Summary: Wrong OData results with multiple self relationships Key: TEIID-4852 URL: https://issues.jboss.org/browse/TEIID-4852 Project: Teiid Issue Type: Bug Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Blocker Fix For: 9.3, 9.1.5, 9.2.2 If an entity has multiple self relationships, only the first foreign key will be used no matter which navigation is queried. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4536) Support create schema with multiple statements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4536?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4536: --------------------------------------- I need to amend my previous comment. The only workable conclusion here is to support the create with multiple statements as just a syntax enhancement without a direct correlation to vdb migration. We allow for additional ddl statements (notably alters) not traditionally supported in a create schema statement, so we shouldn't push toward a non-standard solution. > Support create schema with multiple statements > ---------------------------------------------- > > Key: TEIID-4536 > URL: https://issues.jboss.org/browse/TEIID-4536 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.3 > > > Create schema can support following create statements being directly associated rather than requiring an intermediate use schema > create schema x > create view ... > ... > ; -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4849) Google translator behaves unexpectedly with Double in WHERE clause of SELECT

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIID-4849?page=com.atlassian.jira.plugin... ] Lucie Fabrikova commented on TEIID-4849: ---------------------------------------- In my case, locale of google sheet was set to 'Czechia', for double format '15,1'. If I switch locale to 'UK', it works correctly with teiid double format '15.1'. > Google translator behaves unexpectedly with Double in WHERE clause of SELECT > ---------------------------------------------------------------------------- > > Key: TEIID-4849 > URL: https://issues.jboss.org/browse/TEIID-4849 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > > Query like "SELECT DoubleNum FROM SmallA WHERE DoubleNum > 5.0" gives unexpected results for following values in DoubleNum column: > * value like '15.1' is probably by google spreadsheet interpreted as date (in function row in sheet appears 15.1.2017), SELECT query returns no results > * value like '150.1': SELECT returns null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4849) Google translator behaves unexpectedly with Double in WHERE clause of SELECT

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIID-4849?page=com.atlassian.jira.plugin... ] Lucie Fabrikova commented on TEIID-4849: ---------------------------------------- For me worked to enter decimal number into google sheet as "15,1". > Google translator behaves unexpectedly with Double in WHERE clause of SELECT > ---------------------------------------------------------------------------- > > Key: TEIID-4849 > URL: https://issues.jboss.org/browse/TEIID-4849 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > > Query like "SELECT DoubleNum FROM SmallA WHERE DoubleNum > 5.0" gives unexpected results for following values in DoubleNum column: > * value like '15.1' is probably by google spreadsheet interpreted as date (in function row in sheet appears 15.1.2017), SELECT query returns no results > * value like '150.1': SELECT returns null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4849) Google translator behaves unexpectedly with Double in WHERE clause of SELECT

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIID-4849?page=com.atlassian.jira.plugin... ] Lucie Fabrikova closed TEIID-4849. ---------------------------------- Resolution: Rejected > Google translator behaves unexpectedly with Double in WHERE clause of SELECT > ---------------------------------------------------------------------------- > > Key: TEIID-4849 > URL: https://issues.jboss.org/browse/TEIID-4849 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.10.6_3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > > Query like "SELECT DoubleNum FROM SmallA WHERE DoubleNum > 5.0" gives unexpected results for following values in DoubleNum column: > * value like '15.1' is probably by google spreadsheet interpreted as date (in function row in sheet appears 15.1.2017), SELECT query returns no results > * value like '150.1': SELECT returns null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3411) LDAP translator and multi-valued arrays

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3411: --------------------------------------- TEIIDDES-2910 has not yet been worked, but I would still expect designer to handle the import. At worst the properties should just be associated as generic name value pairs. Please start a Designer thread or issue about this. > LDAP translator and multi-valued arrays > --------------------------------------- > > Key: TEIID-3411 > URL: https://issues.jboss.org/browse/TEIID-3411 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.12 > > > The problem is with how multi-valued attribute from the LDAP response is handled. They don't want to have the data mapped to an array or multivalued-concat and then transformed into another table to get the unique values. There is an issue with the translator as it should handle multivalued attribute, by simply creating multiple rows for each value of the multivalued attribute. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2017