[teiid-issues] [JBoss JIRA] (TEIID-1927) BLOB/CLOB errors while using teiid 7.6 JDBC

[Graeme Gillies (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664680#comment-12664680 ] 

Graeme Gillies commented on TEIID-1927:
---------------------------------------

I can look at getting you a stacktrace. On dbvisualiser it gives the error above, on squirrel it just gives the fields back as <CLOB> without their real value.

I assume this all just means we actually chose the wrong field type MEDIUMTEXT to represent this data. Is there a type we can use instead that allows string comparisons and comes back as datatype string instead of clob?

Regards,

Graeme
                
> BLOB/CLOB errors while using teiid 7.6 JDBC
> -------------------------------------------
>
>                 Key: TEIID-1927
>                 URL: https://issues.jboss.org/browse/TEIID-1927
>             Project: Teiid
>          Issue Type: Bug
>    Affects Versions: 7.6
>         Environment: java version "1.6.0_20"
> OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.23.1.9.10.el5_7-x86_64)
> OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
> Running on RHEL 5, teiid 7.6 inside of JBoss EAP 5.1.1
> Client is SQuirrel SQL client version 3.2.2
> or
> DBVisualiser version FREE 8.0.7
>            Reporter: Graeme Gillies
>            Assignee: Steven Hawkins
>
> Hi,
> We have recently upgraded to teiid 7.6 on our environment, and we have noticed that a few users have been reporting problems querying data via JDBC surrounding blobs/clobs.
> The fields in the VDB model are marked as MEDIUMTEXT, but when trying to run an example query such as
> {noformat}
> select bug_id, keywords from bugzilla.bugs order by bug_id limit 1000;
> {noformat}
> In squirrel you just get the values back as <Clob> (not the real value) and in dbvisualiser you get back CLOB in the field with the following errors
> {noformat}
> [cleared]
> ting clob data: 
> 08:53:42 [ERROR Thread-22 TextData.getData] javax.sql.rowset.serial.SerialException: Invalid position in BLOB object set
> 08:53:42 [ERROR Thread-22 TextData.getData] Error getting clob data: 
> 08:53:42 [ERROR Thread-22 TextData.getData] javax.sql.rowset.serial.SerialException: Invalid position in BLOB object set
> 08:53:42 [ERROR Thread-22 TextData.getData] Error getting clob data: 
> 08:53:42 [ERROR Thread-22 TextData.getData] javax.sql.rowset.serial.SerialException: Invalid position in BLOB object set
> 08:53:42 [ERROR Thread-22 TextData.getData] Error getting clob data: 
> 08:53:42 [ERROR Thread-22 TextData.getData] javax.sql.rowset.serial.SerialException: Invalid position in BLOB object set
> 08:53:42 [ERROR Thread-22 TextData.getData] Error getting clob data: 
> 08:53:42 [ERROR Thread-22 TextData.getData] javax.sql.rowset.serial.SerialException: Invalid position in BLOB object set
> 08:53:42 [ERROR Thread-22 TextData.getData] Error getting clob data: 
> {noformat}
> Another query giving us grief is
> {noformat}
> SELECT
> p.plan_id,
> p.product_id,
> p.author_id,
> p.type_id,
> v.id as default_product_version,
> p.name,
> p.creation_date,
> p.isactive,
> p.extra_link,
> p.parent_id
> FROM testopia.test_plans p
> left join testopia.versions v
> on
> p.product_id = v.product_id and
> p.default_product_version = v.value
> where p.creation_date>= '2012-02-05'
> {noformat}
> which gives the error
> {noformat}
> ERROR:  Expressions of type OBJECT, CLOB, BLOB, or XML cannot be used in comparison: p.default_product_version = v."value".
> DETAIL:  org.teiid.jdbc.TeiidSQLException: Expressions of type OBJECT, CLOB, BLOB, or XML cannot be used in comparison: p.default_product_version = v."value".
> {noformat}
> We updated our VDB models using teiid designer 7.6 at the same time we updated teiid to 7.6, so it could be something we have changed there. Have we got the wrong type set for these fields (should they not be MEDIUMTEXT) or is this a bug in the driver or in teiid?
> Regards,
> Graeme

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira