db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Myrna van Lunteren <m.v.lunte...@gmail.com>
Subject Re: Derby and portability
Date Wed, 16 Nov 2005 21:40:05 GMT
I think we should claim platform independence in this regard. I think
DERBY-588 is the only case where we've run into a db created on one platform
not working elsewhere, and it's listed as a bug. If we don't expect platform
independence in this regard, this would be an enhancement...But I don't
think that is ok - so I filed it as a bug. (and an odd one it is too).

 On 11/16/05, Rajesh Kartha <kartha@source-zone.org> wrote:
> Not sure, but shouldn't the JIRA issue, DERBY-588, be considered when
> we claim the portability of a Derby database.
> Database created in zOS does not boot in Windows due to the encoding of
> the service.properties file.
> http://issues.apache.org/jira/browse/DERBY-588
> -Rajesh
> Mike Matrigali wrote:
> > Currently the on-disk format is platform-independent. I don't see
> > any reason not to make a committment to that going forward.
> >
> > Oyvind.Bakksjo@Sun.COM wrote:
> >
> >> The Derby Project Charter (on the web site) states that it should be
> >> "Pure Java", but it does not say anything about portability for
> >> anything but the _code_.
> >>
> >> Can one, for example, safely assume that the on-disk database format
> >> is platform-independent? I have read it somewhere, but I don't see it
> >> in the charter, so do I have a guarantee that this is an invariant?
> >>
> >

View raw message