db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-2923) Incorrect reading of nullable Blob/Clob columns during soft upgrade with client/server
Date Wed, 11 Jul 2007 13:03:04 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Øystein Grøvlen 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 

> 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: Øystein Grøvlen
>            Assignee: Øystein Grøvlen
>            Priority: Blocker
>             Fix For: 10.3.1.1
>
>         Attachments: SimpleBlobTest.java
>
>
> Select operations with client/server and soft upgrade mode will not see first 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 null 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.

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


Mime
View raw message