db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Farrukh Najmi <Farrukh.Na...@Sun.COM>
Subject Re: A truncation error was encountered tryin,g to shrink BLOB 'XX-RESOLVE-XX' to length 1048576.
Date Tue, 06 Jun 2006 15:03:29 GMT
Daniel John Debrunner wrote:
> Farrukh Najmi wrote:
>
>   
>> Dear Derby team,
>>
>> I am storing a blob into Derby 10.1.2.1 using hibernate and getting this
>> SQLException from Derby (see second stack trace below).
>> The blob is just a gig image of size 1.4MB. This seems well within the
>> 2GB limit for blobs. What is wrong and how can I fix it?
>>     
>
> You probably created the table without specifying a length on BLOB, this
> defaults to BLOB(1M). You need to use BLOB(2G). e.g.
>
> create table T (a int, b BLOB(2G))
>
> A bug about this info missing in the doc was reported as DERBY-769
>
> http://issues.apache.org/jira/browse/DERBY-769
>
> Dan.
>
>
>   
Thank you Dan! That sounds like the problem.
BTW I am curious why the 2G is not the default?
Is there a performance / space downside to specifying BLOB(2G) always?

-- 
Regards,
Farrukh



Mime
View raw message