]
Steven Hawkins commented on TEIID-1927:
---------------------------------------
In most versions of squirrel you can click on the <CLOB> value to see the actual
text.
Your source datatypes are up to your needs. MEDIUMTEXT represents up a character string
with up to 2^24 characters, thus we map it to clob on the chance that the driver can
provide us a memory safe representation. If you choose to represent it with a Teiid
string, it may be limited to 4000 characters depending on how it's
retrieved/manipulated.
TEIID-1834 can be a candidate for back-porting to 7.7 if needed.
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: