db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1384) Increase default BLOB/CLOB length to maximum supported (2G?)
Date Thu, 08 Jun 2006 12:29:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415339 ] 

Bernt M. Johnsen commented on DERBY-1384:

2G is 2G, not 2G-1. See ISO/IEC 9075-2:2003 (E) 6.1 <data type>:

If <large object length> immediately contains <large object length token> or immediately
<unsigned integer> and <multiplier>, then let D be the value of the specified
<unsigned integer> or
the numeric value of the sequence of <digit>s of <large object length token> interpreted
as an <unsigned
integer>. The numeric value of <large object length> is the numeric value resulting
from the multiplication
of D and MS, then MS is:
i) If <multiplier> is K, then 1,024.
ii) If <multiplier> is M, then 1,048,576.
iii) If <multiplier> is G, then 1,073,741,824.

I agree that this might change the behaviour of existing applications, but that the increased
usability is  worth the change.

> 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:
>  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:
For more information on JIRA, see:

View raw message