db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Myrna van Lunteren <m.v.lunte...@gmail.com>
Subject Re: CLOBs (again)
Date Wed, 17 Aug 2005 21:13:48 GMT
Hi Brian,
 ij has a default maximum display width per column of 128. 
If you change it, you will see more.
For instance, 
ij> maximumdisplaywidth 360;
Will return 360 characters.
 Myrna
 On 8/17/05, Brian Bonner <brian.bonner@paraware.com> wrote: 
> 
> Hi again. Here's what I did:
> 
> I create a table in derby via the eclipse plugin.
> 
> connect 'jdbc:derby:clobtest;create=true';
> create table clobber(id int primary key, content clob(100 K));
> 
> insert into clobber values
> 
> (1,'11111111111111111111111111111111111111111111111111111111222222222222222222...');
> with 594 characters in the string.
> 
> but when I do:
> 
> select * from clobber;
> ID
> |CONTENT
> 
> 
> --------------------------------------------------------------------------------------------------------------------------------------------
> 1
> 
> |1111111111111111111111111111111111111111111111111111111122222222222222222222222222222222222222222222222222222222222222222222222&
> 
> I only get 128 characters of the clob back.
> 
> If I change the content field to be a long varchar and run the same
> thing again, I get the same results from IJ, but if I use a different
> tool, (Data Explorer in Eclipse for instance), I get all of the data
> back from the long varchar table, but still only 128 characters in the
> clob side.
> 
> Maybe this is just the limitation of how the clob behaves in both
> tools. I was expecting to see all of the data in both cases.
> 
> Any thoughts on this?
> 
> Brian
> 
> --
> Brian
> 
> 
>

Mime
View raw message