Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 31975 invoked from network); 29 Jul 2009 16:48:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Jul 2009 16:48:38 -0000 Received: (qmail 8175 invoked by uid 500); 29 Jul 2009 16:48:39 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 8119 invoked by uid 500); 29 Jul 2009 16:48:39 -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 8111 invoked by uid 99); 29 Jul 2009 16:48:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2009 16:48:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2009 16:48:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D900E234C051 for ; Wed, 29 Jul 2009 09:48:14 -0700 (PDT) Message-ID: <929039261.1248886094887.JavaMail.jira@brutus> Date: Wed, 29 Jul 2009 09:48:14 -0700 (PDT) From: "Mamta A. Satoor (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4256) allow alter table to increase the maximum size of a blob and a clob. In-Reply-To: <522629521.1244048647465.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736701#action_12736701 ] Mamta A. Satoor commented on DERBY-4256: ---------------------------------------- Eranda, I quickly went through your patch and it looks good to me. Would it be possible to try to create smaller blob/clob columns, increase their size and then insert data which is bigger than the original size but smaller than the new size to see if we are able to store and retrieve bigger data. Once we know this works fine on a standalone case, we should add a junit test to put it into our regression suite for this change. > allow alter table to increase the maximum size of a blob and a clob. > -------------------------------------------------------------------- > > Key: DERBY-4256 > URL: https://issues.apache.org/jira/browse/DERBY-4256 > Project: Derby > Issue Type: Improvement > Components: SQL > Affects Versions: 10.5.1.1 > Reporter: Mike Matrigali > Assignee: Eranda Sooriyabandara > Priority: Minor > Attachments: derby4256.diff, derby4256.diff > > > Allow new syntax that allows user to alter the maximum length of a blob and/or clob column: > ALTER TABLE binarydata ALTER COLUMN data SET DATA TYPE blob(128M) > The syntax should match up with the existing functionality to increase the size of varchar fields. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.