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: pass (nike.apache.org: local policy)
From: dag.wanvik@oracle.com (Dag H. Wanvik)
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: CASE [expression] WHEN [expression] THEN [expression] END syntax
References: <BANLkTin9xc5r+hu79-TJ939Tenf6jYdSHA@mail.gmail.com>
	<4DD56EA6.2060400@oracle.com> <x6d3jeic88.fsf@oracle.com>
	<BANLkTimtrFj9KwZWN=m_2NfwwX1FMDg6Eg@mail.gmail.com>
	<x639k62yy2.fsf@oracle.com>
	<BANLkTi=f6T-DVZhERgWwiO-ZeEZdKxiceA@mail.gmail.com>
	<x1oxlixouuxo.fsf@oracle.com>
	<BANLkTincW4yYtxM_L5jEXA+Fw3q3Fkojxg@mail.gmail.com>
Date: Mon, 30 May 2011 19:08:01 +0200
In-Reply-To: <BANLkTincW4yYtxM_L5jEXA+Fw3q3Fkojxg@mail.gmail.com> (Lukas
	Eder's message of "Mon, 30 May 2011 16:46:29 +0200")
Message-ID: <x1oxd3j0unf2.fsf@oracle.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (usg-unix-v)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Lukas Eder <lukas.eder@gmail.com> writes:

> 2. It took me a while to understand that some of the missing artefacts
> are actually generated (such as the output from sqlgrammar.jj). I
> imagine that can be done with the main build target in the ant
> build.xml

This is correct. "sqlgrammar.jj" is written in the input language to
JavaCC, cf. docs here: http://javacc.java.net/

> 3. After generating, I still had lots of compilation errors. I was not
> sure whether this is

Unfortunately, in order to support older Java versions, the Derby build
and sources contains a fair amount of trickery which makes life hard for
an IDE, I see similar errors using Netbeans: most source is written to
run on Java 1.4.2, while the IDE thinks the code is implementing Java 6,
e.g. for JDBC implementation methods this give me many red flags... I
build using the cmd line + ant.

> 3c. Because of trunk being unstable

Not likely, we have a tinderbox test which quickly uncovers if the build
is broken on trunk.

> And I finally came to the conclusion, that this is a non-trivial task
> for a new contributor, even if you might find it easy :-) Not to
> mention adding test cases and making them run, etc...

Admitted. It it is definitely not just an afternoon's work.

> Apart from that, I'm developing a database abstraction library:
> http://www.jooq.org.
>
> In jOOQ, it was very easy for me to "simulate" the missing CASE
> expression as mentioned above. So my users will be able to run both
> types of CASE expressions on a Derby DB...

Cool! Hopefully we can get this fixed in Derby proper going forward.

Thanks,
Dag