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 (asf.osuosl.org: local policy)
Message-ID: <44F449C7.5080504@intland.com>
Date: Tue, 29 Aug 2006 17:05:59 +0300
From: Robert Enyedi <robert.enyedi@intland.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: NullPointerException in Derby client
References: <44F2DA05.8060707@intland.com>
 <47EA1DC5-8484-4107-B0FB-B45536B9001D@SUN.com> <44F2FB14.5090602@apache.org>
In-Reply-To: <44F2FB14.5090602@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I filed the bug report http://issues.apache.org/jira/browse/DERBY-1774 
with detailed information on how to reproduce this right from inside ij.

Any suggestions on how to avoid this bug would be warmly welcome.

Regards,
Robert

Daniel John Debrunner wrote:
> Craig L Russell wrote:
>
>   
>> Hi Robert,
>>
>> Please file a bug report in the Derby JIRA. Include the stack trace 
>> along with an ij script that creates the tables and a simple jdbc 
>> program that issues the query that causes the NPE.
>>
>> Someone on the Derby dev team will follow up.
>>     
>
> There is no "Derby team", Derby is an open-source community where anyone
> can get involved and work on improving Derby in many ways including
> fixing bugs. People work on what interests them: "fry their own fish" or
> "scratch their own itch". Entering a bug may catch the interest of
> someone already active in the community, but it may not, there is no
> "will" about it. One sure way to get a bug fixed is to work in the
> community on fixing it.
>
> Here's an explanation of how development at Apache works:
>
> http://db.apache.org/derby/derby_comm.html#Understand+How+Development+Works+at+Apache
>
> The community is always ready to welcome new people.
>
> http://wiki.apache.org/db-derby/DerbyDev
>
> Dan.
>
>
>
>
>