July 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5427) Remove session/user scoped materialized views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5427?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5427: --------------------------------------- Yes we cannot share by default across versions unless you have a full analysis of the view and everything contributing to it and ensure that it is the same. > Remove session/user scoped materialized views > --------------------------------------------- > > Key: TEIID-5427 > URL: https://issues.jboss.org/browse/TEIID-5427 > Project: Teiid > Issue Type: Task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > TEIID-2507 added session scoped materialized views - which are now not well aligned with any other materialization strategy. They have to be unmanaged and internal only. It would be best to completely remove the feature and recommend instead that users create global temporary tables instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5363) SimpleDB connector not quoting table names in internal Select queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5363?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5363: --------------------------------------- No, I mean to SimpleDB when you are receiving the exception. > SimpleDB connector not quoting table names in internal Select queries > --------------------------------------------------------------------- > > Key: TEIID-5363 > URL: https://issues.jboss.org/browse/TEIID-5363 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 11.0, 10.3.2 > > > Facing an issue while querying the Simple DB connector for a specific type of tables - the tables that contain a hyphen in the name. > According to the SimpleDB documentation: > Attribute and domain names may appear without quotes if they contain only letters, numbers, underscores (_), or dollar symbols ($) and do not start with a number. You must quote all other attribute and domain names with the backtick (`). > (https://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/QuotingR...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5363) SimpleDB connector not quoting table names in internal Select queries

by Pranav K (JIRA)

[ https://issues.jboss.org/browse/TEIID-5363?page=com.atlassian.jira.plugin... ] Pranav K edited comment on TEIID-5363 at 7/23/18 2:47 AM: ---------------------------------------------------------- You mean the query to the VDB? No, the exact query to the VDB is -> select * from "test_simple"."test-hyph". The query to the VDB would be always be a standard SQL I assume, and the final translated query be of the form that you mention (here test-simple is the source model atop simple db). Running this query is when I get the error mentioned above. Running select `col` from `ta-ble` would anyway result in a Teiid query parsing error right? was (Author: pranavk): You mean the query to the VDB? No, the exact query to the VDB is -> select * from "test_simple"."test-hyph". The query to the VDB would be always be a standard SQL I assume, and the final translated query be of the form that you mention (here test-simple is the source model atop simple db). Running this query is when I get the error mentioned above. > SimpleDB connector not quoting table names in internal Select queries > --------------------------------------------------------------------- > > Key: TEIID-5363 > URL: https://issues.jboss.org/browse/TEIID-5363 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 11.0, 10.3.2 > > > Facing an issue while querying the Simple DB connector for a specific type of tables - the tables that contain a hyphen in the name. > According to the SimpleDB documentation: > Attribute and domain names may appear without quotes if they contain only letters, numbers, underscores (_), or dollar symbols ($) and do not start with a number. You must quote all other attribute and domain names with the backtick (`). > (https://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/QuotingR...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5363) SimpleDB connector not quoting table names in internal Select queries

by Pranav K (JIRA)

[ https://issues.jboss.org/browse/TEIID-5363?page=com.atlassian.jira.plugin... ] Pranav K commented on TEIID-5363: --------------------------------- You mean the query to the VDB? No, the exact query to the VDB is -> select * from "test_simple"."test-hyph". The query to the VDB would be always be a standard SQL I assume, and the final translated query be of the form that you mention (here test-simple is the source model atop simple db). Running this query is when I get the error mentioned above. > SimpleDB connector not quoting table names in internal Select queries > --------------------------------------------------------------------- > > Key: TEIID-5363 > URL: https://issues.jboss.org/browse/TEIID-5363 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 11.0, 10.3.2 > > > Facing an issue while querying the Simple DB connector for a specific type of tables - the tables that contain a hyphen in the name. > According to the SimpleDB documentation: > Attribute and domain names may appear without quotes if they contain only letters, numbers, underscores (_), or dollar symbols ($) and do not start with a number. You must quote all other attribute and domain names with the backtick (`). > (https://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/QuotingR...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5429) timestampadd(SQL_TSI_MONTH, 1, 31/03/2018)) results in ORA-01839: date not valid for month specified

by Ivan Semenov (JIRA)

[ https://issues.jboss.org/browse/TEIID-5429?page=com.atlassian.jira.plugin... ] Ivan Semenov updated TEIID-5429: -------------------------------- Summary: timestampadd(SQL_TSI_MONTH, 1, 31/03/2018)) results in ORA-01839: date not valid for month specified (was: timestampadd(SQL_TSI_MONTH, 1, to_date('2018/03/31', 'yyyy/mm/dd')) results in ORA-01839: date not valid for month specified) > timestampadd(SQL_TSI_MONTH, 1, 31/03/2018)) results in ORA-01839: date not valid for month specified > ---------------------------------------------------------------------------------------------------- > > Key: TEIID-5429 > URL: https://issues.jboss.org/browse/TEIID-5429 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.x > Reporter: Ivan Semenov > Assignee: Steven Hawkins > > There is a known problem with Oracle's intervals: > {code:sql} > select to_date('2018/03/31', 'yyyy/mm/dd') + (INTERVAL '1' MONTH(2)) from dual > {code} > results in {{ORA-01839: date not valid for month specified error}} > As an alternative, ADD_MONTHS function could be used . > {code:sql} > select ADD_MONTHS(to_date('2018/03/31', 'yyyy/mm/dd'), 1) from dual > {code} > It is not defined in the functions spec how timestampadd with SQL_TSI_MONTH should behave in some cases but anyway no error should happen. > Currently "interval" - inflicted Oracle errors are transmitted for timestampadd invocations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5429) timestampadd(SQL_TSI_MONTH, 1, to_date('2018/03/31', 'yyyy/mm/dd')) results in ORA-01839: date not valid for month specified

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5429?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5429: --------------------------------------- Thanks for raising this. It looks like add_months will also handle the leap year case, so I'll map both the months and years interval to add_months. > timestampadd(SQL_TSI_MONTH, 1, to_date('2018/03/31', 'yyyy/mm/dd')) results in ORA-01839: date not valid for month specified > ---------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-5429 > URL: https://issues.jboss.org/browse/TEIID-5429 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.x > Reporter: Ivan Semenov > Assignee: Steven Hawkins > > There is a known problem with Oracle's intervals: > {code:sql} > select to_date('2018/03/31', 'yyyy/mm/dd') + (INTERVAL '1' MONTH(2)) from dual > {code} > results in {{ORA-01839: date not valid for month specified error}} > As an alternative, ADD_MONTHS function could be used . > {code:sql} > select ADD_MONTHS(to_date('2018/03/31', 'yyyy/mm/dd'), 1) from dual > {code} > It is not defined in the functions spec how timestampadd with SQL_TSI_MONTH should behave in some cases but anyway no error should happen. > Currently "interval" - inflicted Oracle errors are transmitted for timestampadd invocations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5429) timestampadd(SQL_TSI_MONTH, 1, to_date('2018/03/31', 'yyyy/mm/dd')) results in ORA-01839: date not valid for month specified

by Ivan Semenov (JIRA)

[ https://issues.jboss.org/browse/TEIID-5429?page=com.atlassian.jira.plugin... ] Ivan Semenov updated TEIID-5429: -------------------------------- Summary: timestampadd(SQL_TSI_MONTH, 1, to_date('2018/03/31', 'yyyy/mm/dd')) results in ORA-01839: date not valid for month specified (was: timestampadd(SQL_TSI_MONTH, 1, "march-31-2000") results in ORA-01839: date not valid for month specified) > timestampadd(SQL_TSI_MONTH, 1, to_date('2018/03/31', 'yyyy/mm/dd')) results in ORA-01839: date not valid for month specified > ---------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-5429 > URL: https://issues.jboss.org/browse/TEIID-5429 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.x > Reporter: Ivan Semenov > Assignee: Steven Hawkins > > There is a known problem with Oracle's intervals: > {code:sql} > select to_date('2018/03/31', 'yyyy/mm/dd') + (INTERVAL '1' MONTH(2)) from dual > {code} > results in {{ORA-01839: date not valid for month specified error}} > As an alternative, ADD_MONTHS function could be used . > {code:sql} > select ADD_MONTHS(to_date('2018/03/31', 'yyyy/mm/dd'), 1) from dual > {code} > It is not defined in the functions spec how timestampadd with SQL_TSI_MONTH should behave in some cases but anyway no error should happen. > Currently "interval" - inflicted Oracle errors are transmitted for timestampadd invocations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5429) timestampadd(SQL_TSI_MONTH, 1, "march-31-2000") results in ORA-01839: date not valid for month specified

by Ivan Semenov (JIRA)

[ https://issues.jboss.org/browse/TEIID-5429?page=com.atlassian.jira.plugin... ] Ivan Semenov edited comment on TEIID-5429 at 7/22/18 9:16 AM: -------------------------------------------------------------- The same issue may take place with SQL_TSI_YEAR on date February 29th. was (Author: isemenov): The same issue may take place with February 29 for non-leap year. > timestampadd(SQL_TSI_MONTH, 1, "march-31-2000") results in ORA-01839: date not valid for month specified > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5429 > URL: https://issues.jboss.org/browse/TEIID-5429 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.x > Reporter: Ivan Semenov > Assignee: Steven Hawkins > > There is a known problem with Oracle's intervals: > {code:sql} > select to_date('2018/03/31', 'yyyy/mm/dd') + (INTERVAL '1' MONTH(2)) from dual > {code} > results in {{ORA-01839: date not valid for month specified error}} > As an alternative, ADD_MONTHS function could be used . > {code:sql} > select ADD_MONTHS(to_date('2018/03/31', 'yyyy/mm/dd'), 1) from dual > {code} > It is not defined in the functions spec how timestampadd with SQL_TSI_MONTH should behave in some cases but anyway no error should happen. > Currently "interval" - inflicted Oracle errors are transmitted for timestampadd invocations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5429) timestampadd(SQL_TSI_MONTH, 1, "march-31-2000") results in ORA-01839: date not valid for month specified

by Ivan Semenov (JIRA)

[ https://issues.jboss.org/browse/TEIID-5429?page=com.atlassian.jira.plugin... ] Ivan Semenov commented on TEIID-5429: ------------------------------------- The same issue may take place with February 29 for non-leap year. > timestampadd(SQL_TSI_MONTH, 1, "march-31-2000") results in ORA-01839: date not valid for month specified > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5429 > URL: https://issues.jboss.org/browse/TEIID-5429 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.x > Reporter: Ivan Semenov > Assignee: Steven Hawkins > > There is a known problem with Oracle's intervals: > {code:sql} > select to_date('2018/03/31', 'yyyy/mm/dd') + (INTERVAL '1' MONTH(2)) from dual > {code} > results in {{ORA-01839: date not valid for month specified error}} > As an alternative, ADD_MONTHS function could be used . > {code:sql} > select ADD_MONTHS(to_date('2018/03/31', 'yyyy/mm/dd'), 1) from dual > {code} > It is not defined in the functions spec how timestampadd with SQL_TSI_MONTH should behave in some cases but anyway no error should happen. > Currently "interval" - inflicted Oracle errors are transmitted for timestampadd invocations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5429) timestampadd(SQL_TSI_MONTH, 1, "march-31-2000") results in ORA-01839: date not valid for month specified

by Ivan Semenov (JIRA)

Ivan Semenov created TEIID-5429: ----------------------------------- Summary: timestampadd(SQL_TSI_MONTH, 1, "march-31-2000") results in ORA-01839: date not valid for month specified Key: TEIID-5429 URL: https://issues.jboss.org/browse/TEIID-5429 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 11.x Reporter: Ivan Semenov Assignee: Steven Hawkins There is a known problem with Oracle's intervals: {code:sql} select to_date('2018/03/31', 'yyyy/mm/dd') + (INTERVAL '1' MONTH(2)) from dual {code} results in {{ORA-01839: date not valid for month specified error}} As an alternative, ADD_MONTHS function could be used . {code:sql} select ADD_MONTHS(to_date('2018/03/31', 'yyyy/mm/dd'), 1) from dual {code} It is not defined in the functions spec how timestampadd with SQL_TSI_MONTH should behave in some cases but anyway no error should happen. Currently "interval" - inflicted Oracle errors are transmitted for timestampadd invocations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2018