db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2923) Incorrect reading of nullable Blob/Clob columns during soft upgrade with client/server
Date Fri, 13 Jul 2007 12:01:06 GMT

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

Knut Anders Hatlen resolved DERBY-2923.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.4.0.0
       Derby Info: [Regression]  (was: [Regression, Patch Available])

Committed to 10.3 with revision 555949.
Merged to trunk and committed revision 555956.

> 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.2, 10.4.0.0
>
>         Attachments: SimpleBlobTest.java, softupgradefix.diff
>
>
> 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