November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3586: ---------------------------------- > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3586: --------------------------------- Fix Version/s: 8.7.2.6_2 (was: 8.7.1.6_2) > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.2, 8.7.2.6_2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3592: --------------------------------- Fix Version/s: 8.7.2.6_2 (was: 8.7.1.6_2) > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.2, 8.7.2.6_2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2936) Combining multiple 'in' criteria can prevent pushing criteria to database

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2936?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2936: --------------------------------- Fix Version/s: 8.7.2.6_2 (was: 8.7.1.6_2) > Combining multiple 'in' criteria can prevent pushing criteria to database > ------------------------------------------------------------------------- > > Key: TEIID-2936 > URL: https://issues.jboss.org/browse/TEIID-2936 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.7 > Reporter: Mike Higgins > Assignee: Steven Hawkins > Fix For: 8.8, 8.7.2.6_2 > > > When two 'in' criteria containing constant values on the same field are combined with an 'or', Teiid will combine the two into a single 'in' operation. > Since Oracle (for example) has a 1000 item limit on the 'in' values, if the resulting combined list contains more than 1000 values, it can no longer be pushed down into Oracle for execution. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3586: --------------------------------- Fix Version/s: 8.7.1.6_2 > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3586. -------------------------------- Resolution: Done > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.11.2, 8.12, 8.7.1.6_2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3592: ---------------------------------- > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3592) XMLFOREST returns source rather than view column names

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3592?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3592: --------------------------------- Fix Version/s: 8.7.1.6_2 > XMLFOREST returns source rather than view column names > ------------------------------------------------------ > > Key: TEIID-3592 > URL: https://issues.jboss.org/browse/TEIID-3592 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.12, 8.11.2 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3586) Literal date comparisons with databasetimezone set are incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3586?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3586: ---------------------------------- > Literal date comparisons with databasetimezone set are incorrect > ---------------------------------------------------------------- > > Key: TEIID-3586 > URL: https://issues.jboss.org/browse/TEIID-3586 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.2 > > > If the database timezone property is set and a literal comparison is used, then the date value will be shifted from the local timezone into the database timezone, but it should be the other way around. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3808) Informix translator - date/time/timestamp values are adjusted differently according to timezone

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3808?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3808: ------------------------------------- OK. Let's add a KI. If server's timezone is set to GMT+0 then no value is adjusted and application can adjust it by itself. > Informix translator - date/time/timestamp values are adjusted differently according to timezone > ----------------------------------------------------------------------------------------------- > > Key: TEIID-3808 > URL: https://issues.jboss.org/browse/TEIID-3808 > Project: Teiid > Issue Type: Quality Risk > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > The Informix translator adjusts only time value according to server's timezone. Timestamp values are adjusted only if 'DatabaseTimeZone' property is set. Date values are not adjusted at all. > I am not sure what is Teiid's logic in this case. Is the difference between server's timezone and database's timezone taken into account? Or only the timezone of the database? > ------------------- > Server's timezone - GMT+1 > DatabaseTimeZone property - not overridden > Result: > |time|date|timestamp| > |01:00:00|2000-01-01|2000-01-01 00:00:00.0| > Server's timezone - GMT+5 > DatabaseTimeZone property - not overridden > Result: > |time|date|timestamp| > |05:00:00|2000-01-01|2000-01-01 00:00:00.0| > Server's timezone - GMT+5 > DatabaseTimeZone property - GMT+1 > Result: > |time|date|timestamp| > |01:00:00|2000-01-01|2000-01-01 04:00:00.0| > Server's timezone - GMT+5 > DatabaseTimeZone property - GMT-1 > Result (int this case > |time|date|timestamp| > |23:00:00|2000-01-01|2000-01-01 06:00:00.0| > Informix: > {code:sql} > ... > datevalue date, > timevalue datetime hour to fraction(1), > timestampvalue datetime year to fraction(1), > ... > {code} > VDB - foreign table: > {code:sql} > ... > DateValue date OPTIONS (NATIVE_TYPE 'date', NAMEINSOURCE 'datevalue'), > TimeValue timestamp OPTIONS (NATIVE_TYPE 'datetime hour to fraction(1)', NAMEINSOURCE 'timevalue'), > TimestampValue timestamp OPTIONS (NATIVE_TYPE 'datetime year to fraction(1)', NAMEINSOURCE 'timestampvalue'), > ... > {code} > VDB - view: > {code:sql} > ... > DateValue date, > TimeValue time, > TimestampValue timestamp, > ... > AS ... DateValue, convert(TimeValue, time), TimestampValue, ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2015