You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Brian Bonner <br...@paraware.com> on 2005/08/17 22:21:13 UTC
CLOBs (again)
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
Re: CLOBs (again)
Posted by Brian Bonner <br...@paraware.com>.
Myrna, thanks. I may jhave read that somewhere. I'll try to change it
and see. I suspect that only the varchar field will return the full 594
and the clob field will still be truncated. I'll try it shortly and
shout back. Thanks, again.
Brian
On Wed, 17 Aug 2005 5:22 pm, Myrna van Lunteren wrote:
> 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
> [mailto: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
>
- Brian (mobile)
ask me about my Sidekick
Re: CLOBs (again)
Posted by Brian Bonner <br...@paraware.com>.
Myrna, I changed the maximumdisplaywidth to 600 and IJ is returning the
correct values for the clob field. Thanks again.
Brian
Myrna van Lunteren wrote:
> 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
> <ma...@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
>
>
>
Re: CLOBs (again)
Posted by Myrna van Lunteren <m....@gmail.com>.
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 <br...@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
>
>
>