Bug 854193 - Exception in TEIID when looking up category_id's
Exception in TEIID when looking up category_id's
Status: CLOSED NOTABUG
Product: TCMS
Classification: Other
Component: Database (Show other bugs)
3.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: jianchen
tools-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-04 06:05 EDT by Chris Ward
Modified: 2012-09-17 03:04 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-09-17 03:04:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Ward 2012-09-04 06:05:13 EDT
Description of problem:

This might be a problem in TEIID rather than TCMS, but i'm not entirely sure.

Running the following command in TEIID (ie, VDBD)

SELECT case_id, component_id FROM Testopia.test_case_components
---------------------------------------------------------------------------
DataError                                 Traceback (most recent call last)
... in <module>()
----> 1 "SELECT case_id, component_id FROM Testopia.test_case_components"

DataError: Error Code:22003 Message:TestopiaDS: Error Code:22003 Message:Unexpected exception while translating results: '48790.0' in column '2' is outside valid range for the datatype SMALLINT.
DETAIL:  org.teiid.jdbc.TeiidSQLException: Error Code:22003 Message:TestopiaDS: Error Code:22003 Message:Unexpected exception while translating results: '48790.0' in column '2' is outside valid range for the datatype SMALLINT.


One workaround to get the query to work, is:

SELECT case_id, CONVERT(component_id, integer) FROM Testopia.test_case_components

But ideally, this workaround wouldn't be required...
Comment 1 yawei Li 2012-09-17 03:04:37 EDT
Component_id is int type, no error in tcms Database.

Note You need to log in before you can comment on or make changes to this bug.