[Hsqldb-developers] Re: [Hsqldb-user] Including null rows in select - bug, option or correct behaviour?

[Fred T. <ft...@cl...>]

This shouldn't be too difficult to change. Classes such as Expression and
Select are responsible for building the results. We will only get involved
if the purpose is a proper implementation of JDO. If you want to help, as a
first step please submit a full list of changes that are required for JDO,
including public interfaces and internal modifications. We can move from
there.

Fred Toussi

PS: Please note the list address: hsq...@so...

Michael Vorburger wrote:

Any chance you could point me in
the right direction where in the source code we could "patch" this
ourselves?

PS: As quick background, we are evaluting the use of hsqldb as
embedded datastore for a JDO-based application.  According to the JDO
specification, comparison with null attributes should exclude elements
from a result set.  Of course you could argue "that's not our
problem", and strictly technically speaking I of course agree, however
if there is a way around this, it would be great, and I believe could
give hsqldb more visibility in the JDO community.  I am willing to put
in some time to help here...