db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre" <mcintyr...@gmail.com>
Subject Re: Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.
Date Mon, 21 Aug 2006 17:41:38 GMT
On 8/21/06, Daniel John Debrunner <djd@apache.org> wrote:
> Andrew McIntyre wrote:
>
> > On 8/20/06, Satheesh Bandaram (JIRA) <derby-dev@db.apache.org> wrote:
> >
> >>
> >> 3) Looks like the code uses generics, which limit the use to JDK 1.5
> >> platforms. While this may be ok, need to document need for JDK 1.5
> >> platform and raise appropriate message if used in earlier platforms.
> >> Most of derby can still run on JDK 1.3 platforms, though not required
> >> for new indepedent modules.
> >
> >
> > As well as being documented, the tool should print a useful error and
> > then exit if a user attempts to run it on an unsupported JVM.
>
> I wouldn't put that as a hard requirement. You can end up with some
> amount of hard to understand code for no benefit. Do we really need to
> test for jdk 1.0, 1.1?, 1.2? How about J2ME/CLDC? Java Card? How about
> J2ME/CDC without foundation profile?
>
> Sometimes it's cleaner and easier just to state in the documentation
> that it requires JDK 1.5 or higher and if someone tries to run it on an
> unsupported platform that's their issue.

Wouldn't:

if (JVMInfo.JDK_ID < JVMInfo.J2SE_15) {
 ... print error and exit ...
}

cover all of those cases and be clear as to the intention, especially
since there's an associated error message?

andrew

Mime
View raw message