Re: [Hsqldb-user] select min in an indexed column containing null values

[Fred T. <fr...@us...>]

Your workaround is fine.

An optimisation takes place when an index is present. This is not
working correctly if there is no condition on the SELECT. It will be
fixed for the next release.

Thanks for reporting. Please use version 2.2.8 as this version has some
other bug fixes.

Fred

On Fri, Jan 27, 2012, at 14:35, sbregent wrote:
> Hello,
>
> I just discovered this point, using hsql 2.2.6:
>
> Given a "Z" column , type_name= Double, is_nullable_true, containing
> values between 0 and 750 and some null values.
>
>
> the query SELECT MIN(Z) from myTable returns
> - 0 if the column is not indexed
> - null if the column is indexed
>
> If the column is indexed, the query SELECT MIN(Z), MIN(Z)+MAX(Z) from
> myTable returns 0, 750 which is correct
>
> I modified my query to SELECT MIN(Z) from myTable WHERE Z is not null
> to avoid the null bad result.
>
> I found nothing about this in the forum. Is this behaviour already
> known? Is it normal?
>
> Thanks in advance,
>
> Sophie
>
> ----------------------------------------------------------------------
> --------
> Try before you buy = See our experts in action! The most comprehensive
> online learning library for Microsoft developers is just $99.99!
> Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style
> Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Hsqldb-user mailing list Hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-user
>