Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <10284311.1184158984465.JavaMail.jira@brutus>
Date: Wed, 11 Jul 2007 06:03: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] Updated: (DERBY-2923) Incorrect reading of nullable
 Blob/Clob columns during soft upgrade with client/server
In-Reply-To: <10678536.1184158444526.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-2923?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

=C3=98ystein Gr=C3=B8vlen updated DERBY-2923:
-----------------------------------

    Attachment: SimpleBlobTest.java

This application can be used to reproduce the problem.  Do as follows.

1. Create a database with 10.2, and disconnect.
2. Start a 10.3 server.
3. Run attached application using the 10.3 derbyclient.jar=20

> Incorrect reading of nullable Blob/Clob columns during soft upgrade with =
client/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
>
>         Attachments: SimpleBlobTest.java
>
>
> Select operations with client/server and soft upgrade mode will not see f=
irst byte of the Blob/Clob if the LOB column is nullable.
> The reason seems to be that during soft upgrade, the network server does =
not prepend the LOB data with the byte indicating whether the column is nul=
l or not.  Hence, the first data byte will be interpreted by the client as =
the 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.