Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <10678536.1184158444526.JavaMail.jira@brutus>
Date: Wed, 11 Jul 2007 05:54:04 -0700 (PDT)
From: =?utf-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-2923) Incorrect reading of nullable
 Blob/Clob columns during soft upgrade with client/server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Incorrect reading of nullable Blob/Clob columns during soft upgrade with cl=
ient/server
---------------------------------------------------------------------------=
-----------

                 Key: DERBY-2923
                 URL: https://issues.apache.org/jira/browse/DERBY-2923
             Project: Derby
          Issue Type: Bug
          Components: Network Server
    Affects Versions: 10.3.0.0, 10.3.1.0, 10.3.1.1
         Environment: Client/server soft upgrade
            Reporter: =C3=98ystein Gr=C3=B8vlen
            Assignee: =C3=98ystein Gr=C3=B8vlen
            Priority: Blocker
             Fix For: 10.3.1.1


Select operations with client/server and soft upgrade mode will not see fir=
st byte of the Blob/Clob if the LOB column is nullable.

The reason seems to be that during soft upgrade, the network server does no=
t prepend the LOB data with the byte indicating whether the column is null =
or not.  Hence, the first data byte will be interpreted by the client as th=
e null byte, and the reading of the LOB will start at the second byte.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.