>>>>>>>>>>>> Sunitha Kambhampati (JIRA) wrote (2006-06-08 18:40:30):
>     [ 
> http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415400 
> ] 
> 
> Sunitha Kambhampati commented on DERBY-1384:
> --------------------------------------------
> 
> Please note: that our interfaces like
> DataTypeDescriptor.getMaximumWidth() etc currently return an int
> . Any change to the clob/blob to be actually 2G (ie 2147483648)
> means we exceed the max value possible for int and it might be
> necessary to change the interfaces to take long instead of  int. 

Derby supports up to 2147483647 (2G-1) so that should not be a
problem. Today Derby also for user convenience interprets 2G as 2G-1.


> 
> > Increase default BLOB/CLOB length to maximum supported (2G?)
> > ------------------------------------------------------------
> >
> >          Key: DERBY-1384
> >          URL: http://issues.apache.org/jira/browse/DERBY-1384
> >      Project: Derby
> >         Type: Improvement
> 
> >   Components: SQL
> >     Reporter: Bernt M. Johnsen
> >     Assignee: Bernt M. Johnsen
> >     Priority: Minor
> >      Fix For: 10.2.0.0
> >  Attachments: derby-1384-code.diff, derby-1384-code.stat, 
> > derby-1384-docs.diff, derby-1384-docs.stat
> >
> > Default BLOB/CLOB length should be the maximum length supported by Derby 
> > (2G?)
> 
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira
> 

-- 
Bernt Marius Johnsen, Database Technology Group, 
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway

Attachment: signature.asc
Description: Digital signature

Reply via email to