Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (athena.apache.org: 32.97.182.146 is neither permitted
 nor denied by domain of qozinx@gmail.com)
Message-ID: <47BF2429.5060407@gmail.com>
Date: Fri, 22 Feb 2008 11:36:09 -0800
From: Army <qozinx@gmail.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [jira] Updated: (DERBY-3330) provide support for unique
 constraint
 over nullable columns
References: <953582638.1203700159726.JavaMail.jira@brutus>
 <47BF10A7.50008@sbcglobal.net> <47BF13A8.6090908@sun.com>
 <47BF1DFC.6050407@sbcglobal.net>
In-Reply-To: <47BF1DFC.6050407@sbcglobal.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Mike Matrigali wrote:
> This would mean either dropping/recreating the index at alter time or
> adding a new store interface to "convert" from old index type to new
> index type.

I haven't been following this discussion at all, but for what it's 
worth, this same sort of question came up in the context of DERBY-3299. 
  I went with the simple approach of dropping the old index and creating 
the new one, so some logic for that kind of thing is now in the 10.4 
codeline.  I plan to build on that a bit more for DERBY-2204, though the 
latter changes probably won't be in for 10.4.

The changes for DERBY-3299 are entirely language-layer, but perhaps it's 
something that can be used here?  Again, I don't really know since I 
haven't been on top of this issue, but I thought I'd mention it...

Army