November 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3223: ------------------------------------- I have changed data type in SQL Server 2012 DB to time. Now I am getting an exception: com.microsoft.sqlserver.jdbc.SQLServerException: The data types time and datetime are incompatible in the less than operator. > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3223: --------------------------------------- So based upon the above, you need to change the modeled type to timestamp or change the database to use a time type. > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3223: --------------------------------------- I believe what is happening then is that the database type is not a time type for 2008 and 2012. There is compensation logic for 2005 and older to have columns modeled as time type, but be effectively mapped to a timestamp (as there was no time type). But with later SQL Servers we expect that if you use the time type the source column will be a time type - otherwise there is a likely a mismatch in that SQL Server assumes a default date of 1900-01-01 vs. JDBC which assumes 1970-01-01. > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3223: ------------------------------------- SQL 2012: StringNum - varchar CharValue - char DoubleNum - decimal BigIntegerValue - decimal ShortValue - decimal FloatNum - float ObjectValue - text IntNum - decimal BigDecimalValue - decimal LongNum - decimal BooleanValue - bit TimestampValue - datetime ByteNum - decimal IntKey - decimal StringKey - varchar TimeValue - datetime DateValue - datetime SQL 2008: IntKey - decimal StringKey - varchar IntNum - decimal StringNum - varchar FloatNum - float LongNum - decimal DoubleNum - decimal ByteNum - decimal DateValue - datetime TimeValue - datetime TimestampValue - datetime BooleanValue - bit CharValue - char ShortValue - decimal BigIntegerValue - decimal BigDecimalValue - decimal ObjectValue - text SQL 2005: IntKey - decimal StringKey - varchar IntNum - decimal StringNum - varchar FloatNum - float LongNum - decimal DoubleNum - decimal ByteNum - decimal DateValue - datetime TimeValue - datetime TimestampValue - datetime BooleanValue - bit CharValue - char ShortValue - decimal BigIntegerValue - decimal BigDecimalValue - decimal ObjectValue - text > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ] Jan Stastny updated TEIID-3215: ------------------------------- Description: With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.) Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does. A - 1. Copy the vdbname-vdb.xml into deployments folder 2. Start the server B - 1. Start the server 2. Copy the vdbname-vdb.xml into deployments folder That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table,...) was: With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.) Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does. A - 1. Copy the vdbname-vdb.xml into deployments folder 2. Start the server B - 1. Start the server 2. Copy the vdbname-vdb.xml into deployments folder That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...) > External Materialization ON_VDB_START_SCRIPT invocation issues > -------------------------------------------------------------- > > Key: TEIID-3215 > URL: https://issues.jboss.org/browse/TEIID-3215 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.7.1, 8.9 > > > With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.) > Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does. > A - 1. Copy the vdbname-vdb.xml into deployments folder > 2. Start the server > B - 1. Start the server > 2. Copy the vdbname-vdb.xml into deployments folder > That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table,...) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-3223: ------------------------------------- sqljdbc4.jar I have discovered this problem using static VDBs. There was no problem with static SQL 2005 VDB. Only with static SQL 2008 and 2012. > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3223: --------------------------------------- Also SQL Server 2005 did not have a time type, so how was this test run there? > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3223?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3223: --------------------------------------- What SQL Server client version are you using, and what does the source sql look like? > An issue with time in WHERE clause - SQLServer > ---------------------------------------------- > > Key: TEIID-3223 > URL: https://issues.jboss.org/browse/TEIID-3223 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Environment: OS: fedora20 > arch: x86_64 > java: oracle 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Teiid is not able to manage WHERE clause with time value. > translator: sqlserver > base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3223) An issue with time in WHERE clause - SQLServer

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3223: ----------------------------------- Summary: An issue with time in WHERE clause - SQLServer Key: TEIID-3223 URL: https://issues.jboss.org/browse/TEIID-3223 Project: Teiid Issue Type: Bug Affects Versions: 8.7.1 Environment: OS: fedora20 arch: x86_64 java: oracle 1.7 Reporter: Juraj Duráni Assignee: Steven Hawkins Teiid is not able to manage WHERE clause with time value. translator: sqlserver base DB: SQL Server 2012/2008/2005 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3219) Excel Translator Wrong Result From Columns With Interleaved Null Values

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-3219?page=com.atlassian.jira.plugin... ] Jan Stastny updated TEIID-3219: ------------------------------- Attachment: artifacts.zip I enclose sheet and vdb. To check the behaviour query a column where there is a null value. For check of multiple columns with null value withing single row, look at the line number 20 in the sheet. > Excel Translator Wrong Result From Columns With Interleaved Null Values > ----------------------------------------------------------------------- > > Key: TEIID-3219 > URL: https://issues.jboss.org/browse/TEIID-3219 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Attachments: artifacts.zip > > > When querying a column which has a null value somewhere in it, the result set is missing all the rows under the null value in the xlsx file. When querying more columns, the result set is missing some values only if there is a row, where both columns contains null value. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 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 2014