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)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Date: Sun, 24 May 2009 19:05:36 +0200
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: Showstopper bug in 10.5.1.1?
In-reply-to: <kk5ivy.tcwvy@email.bg>
Sender: Knut.Hatlen@Sun.COM
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <x6tz3atorj.fsf@Sun.COM>
References: <kk5ivy.tcwvy@email.bg>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.93 (usg-unix-v)

tsvetozar ---- <tsvetozar@email.bg> writes:

> sorry for the late reply, but I wanted to test it some more. here is the stack
> trace I am getting:
>
> java.sql.SQLException: Java exception: ': java.lang.NullPointerException'.
[...]
> the query is a simple SELECT * from ... with an order by on an index. there
> are 2 clob, 2 blob, 1 long varchar and a few more varchar(with-limit) fields
> in table.

Thanks, I'm able to reproduce this problem and have filed a bug report:
https://issues.apache.org/jira/browse/DERBY-4245

By the way, you mentioned that the ORDER BY was on an index, but the
stack trace indicates that the index is not used (the NPE is thrown
while sorting the result, but no sorting should be performed if the
index is used for ordering). You may want to check that you actually
have an index on the ORDER BY column and that the index has the same
ordering as specified by the ORDER BY clause. For instance, an ascending
index on column X cannot be used to order the result descending by
column X.

-- 
Knut Anders