db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2864) LOB import unexpectedly succeeds on corrupt data
Date Fri, 22 Jun 2007 18:12:26 GMT
LOB import unexpectedly succeeds on corrupt data
------------------------------------------------

                 Key: DERBY-2864
                 URL: https://issues.apache.org/jira/browse/DERBY-2864
             Project: Derby
          Issue Type: Bug
    Affects Versions: 10.3.1.0
            Reporter: Rick Hillegas
             Fix For: 10.3.1.1


I exported a lob-bearing table using the SYSCS_UTIL.SYSCS_EXPORT_TABLE_LOBS_TO_EXTFILE procedure.
Then I edited the export file to change the length of one of the lobs to an absurdly large
number (500K). Then I ran SYSCS_UTIL.SYSCS_IMPORT_DATA_LOBS_FROM_EXTFILE. I expected this
command would fail while trying to read beyond the end of the lob file. However, it succeeded.

I think that the import should fail, and the user should see an exception which identifies
the line number and column number holding the corrupt lob pointer. I will attach a test case.

-- 
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