Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 21100 invoked from network); 1 Aug 2007 00:04:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Aug 2007 00:04:15 -0000 Received: (qmail 68068 invoked by uid 500); 1 Aug 2007 00:04:14 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 67642 invoked by uid 500); 1 Aug 2007 00:04:13 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 67596 invoked by uid 99); 1 Aug 2007 00:04:13 -0000 Received: from Unknown (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jul 2007 17:04:13 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2007 00:04:13 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DA69C71404B for ; Tue, 31 Jul 2007 17:03:52 -0700 (PDT) Message-ID: <17077817.1185926632868.JavaMail.jira@brutus> Date: Tue, 31 Jul 2007 17:03:52 -0700 (PDT) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-2864: ---------------------------------- Component/s: SQL > LOB import unexpectedly succeeds on corrupt data > ------------------------------------------------ > > Key: DERBY-2864 > URL: https://issues.apache.org/jira/browse/DERBY-2864 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.3.1.0 > Reporter: Rick Hillegas > 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.