[JBoss JIRA] (TEIID-3219) Excel Translator Wrong Result From Columns With Interleaved Null Values
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3219?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3219:
-------------------------------------
[~kylin] If you already have the fix, please send the pull request along with your above test code
> 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)
9 years, 11 months
[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:
---------------------------------------
Actually that is still happening with their latest driver as well, so that will need a fix.
To recap it is expected with SQL Server 2005 and older that if you have a source model with a time type, that we will convert that to the representative datetime since those versions of SQL Server lack a time type - this is somewhat legacy behavior as we should avoid doing type manipulation at the source model as it's more correct to introduce a view layer. For SQL Server 2008 and later the logic expects the source time to be a time value is currently putting non-bind literal timestamp values in as the JDBC escape value {t '....'} - which does work against JTDS. However the SQL Server 4.0 driver up to the latest (4.0.2206.100) will convert the time escape instead into a timestamp and cause an exception.
> 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)
9 years, 11 months
[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 edited comment on TEIID-3223 at 11/18/14 9:16 AM:
---------------------------------------------------------------
I have changed data type in SQL Server 2012 DB to time. Now I am getting an exception (dynamic VDB):
com.microsoft.sqlserver.jdbc.SQLServerException: The data types time and datetime are incompatible in the less than operator.
was (Author: jdurani):
I have changed data type in SQL Server 2012 DB to time (dynamic VDB). 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)
9 years, 11 months
[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 edited comment on TEIID-3223 at 11/18/14 9:16 AM:
---------------------------------------------------------------
I have changed data type in SQL Server 2012 DB to time (dynamic VDB). Now I am getting an exception:
com.microsoft.sqlserver.jdbc.SQLServerException: The data types time and datetime are incompatible in the less than operator.
was (Author: jdurani):
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)
9 years, 11 months