Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <43F41880.4040401@Sourcery.Org>
Date: Wed, 15 Feb 2006 22:15:28 -0800
From: Satheesh Bandaram <satheesh@Sourcery.Org>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: is DERBY-854 related to the recently fixed issue with readonly
 databases and upgrade?
References: <5F3EBBC316C84F49A35B29023D459932E91052@SLNTEXG.quadrian.com>
 <43F378A0.2010409@sbcglobal.net>
In-Reply-To: <43F378A0.2010409@sbcglobal.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Mike, I missed your question... which was in the subject. The issue I
fixed is different... It was about soft upgrade failing on readonly
database.

Satheesh

Mike Matrigali wrote:

>
> Alex Miller wrote:
>
>> I think DERBY-854 (https://issues.apache.org/jira/browse/DERBY-854) is
>> critical for working with read-only databases in embedded mode.
>> Currently, the JDBC DatabaseMetaData methods are completely broken when
>> running in this mode.  Thus, read-only databases cannot work with any
>> tool that imports metadata (which includes most JDBC tools I'm aware
>> of). 
>> Please vote for this bug if you would like to use read-only databases
>> from a zip file.  My company would love to ship some example databases
>> in this way but have given up on Derby due to this bug. 
>> Alex Miller
>> Chief Architect
>> MetaMatrix
>>
>>
>>
>> -----Original Message-----
>> From: Rick Hillegas [mailto:Richard.Hillegas@Sun.COM] Sent: Tuesday,
>> February 14, 2006 12:13 PM
>> To: Derby Discussion; Derby Development
>> Subject: upcoming 10.2 release
>>
>> Dear Derby user community,
>>
>> Yesterday, the Derby developers started a discussion about the timing
>> and contents of the next (10.2) release. A feature freeze date of April
>> 7 was suggested although we have not settled on this date yet. I would
>> estimate that the actual release would appear around two months after
>> feature freeze.
>>
>> Please let us know about any bugs which are particularly important to
>> you and which you would like to see fixed in this release.
>>
>> Thanks,
>> -Rick
>>
>>
>
>
>