Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A42869B13 for ; Fri, 15 Jun 2012 12:18:22 +0000 (UTC) Received: (qmail 46218 invoked by uid 500); 15 Jun 2012 12:18:22 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 46173 invoked by uid 500); 15 Jun 2012 12:18:22 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 46149 invoked by uid 99); 15 Jun 2012 12:18:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2012 12:18:21 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [59.167.240.32] (HELO fish.ish.com.au) (59.167.240.32) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2012 12:18:12 +0000 Received: from ip-136.ish.com.au ([203.29.62.136]:51494) by fish.ish.com.au with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from ) id 1SfVT9-0000zN-2a; Fri, 15 Jun 2012 22:17:40 +1000 X-CTCH-RefID: str=0001.0A150204.4FDB27E4.00BA,ss=1,re=0.000,fgs=0 Message-ID: <4FDB27E3.9060901@apache.org> Date: Fri, 15 Jun 2012 22:17:39 +1000 From: Aristedes Maniatis User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120529 Thunderbird/13.0 MIME-Version: 1.0 To: derby-user@db.apache.org Subject: Changing collation Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit It looks like this feature is not getting much attention: https://issues.apache.org/jira/browse/DERBY-5179 Is there any workaround to changing collations on a database without dumping all the data and reimporting it into a new database? Can we just drop all the indexes or something and force them to rebuild? We have quite a few customer databases (many over 100Mb) with BLOBS and other troublesome columns, which would be a real nuisance to have to write an automated export/import script for just to make the text fields case insensitive. Is there another way? Thanks Ari -- --------------------------> Aristedes Maniatis GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A