Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <5448890.1183412644467.JavaMail.jira@brutus>
Date: Mon, 2 Jul 2007 14:44:04 -0700 (PDT)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2864) LOB import unexpectedly succeeds on
 corrupt data
In-Reply-To: <29746647.1182535946336.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509689 ] 

Myrna van Lunteren commented on DERBY-2864:
-------------------------------------------

Does this need to be fixed in 10.3.1.1?
If not, I'll unset the fix-in...

> 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
>
>         Attachments: importLobBug.tar
>
>
> 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.