Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 50062 invoked from network); 6 Sep 2005 17:54:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Sep 2005 17:54:06 -0000 Received: (qmail 39933 invoked by uid 500); 6 Sep 2005 17:54:05 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 39891 invoked by uid 500); 6 Sep 2005 17:54:04 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 39878 invoked by uid 99); 6 Sep 2005 17:54:04 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2005 10:54:04 -0700 X-ASF-Spam-Status: No, hits=2.3 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,HTML_30_40,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [206.190.37.77] (HELO web81302.mail.yahoo.com) (206.190.37.77) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 06 Sep 2005 10:54:16 -0700 Received: (qmail 70747 invoked by uid 60001); 6 Sep 2005 17:53:59 -0000 Message-ID: <20050906175359.70745.qmail@web81302.mail.yahoo.com> Received: from [32.97.110.142] by web81302.mail.yahoo.com via HTTP; Tue, 06 Sep 2005 10:53:59 PDT Date: Tue, 6 Sep 2005 10:53:59 -0700 (PDT) From: Susan Cline Subject: Re: SQuirrelSQL & Derby To: Derby Development In-Reply-To: <090620051720.9823.431DCFF9000324570000265F220076370498980B9A01040C0C030A0C0E@comcast.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-609983840-1126029239=:69046" Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --0-609983840-1126029239=:69046 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, Yes, SQuirreL can be used to connect to Derby successfully with the Derby embedded driver, and the Derby network client driver. For additional information about using SQuirreL and Derby, see the Derby web site: http://db.apache.org/derby/integrate/misc.html The 'Product List' is the place to look for this information. As of June 2005, using SQuirreL 2.0rc1 and Derby with the Derby network client driver, there was a problem with result sets. A new jar file, created to resolve this problem, is available for download. However, I just looked at the SQuirreL site and the 2.0 final version has been released. It's likely this release of SQuirreL has the fix for the problem with result sets. Susan acemccloudxx@comcast.net wrote: Has anyone tried to use the SQirrel program with Derby? Was it a success or a failure? --0-609983840-1126029239=:69046 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Hi,
 
Yes, SQuirreL can be used to connect to Derby successfully with the Derby embedded driver, and the Derby network client driver.  For additional information about
using SQuirreL and Derby, see the Derby web site:
 
 
The 'Product List' is the place to look for this information.   As of June 2005, using SQuirreL 2.0rc1 and Derby with the Derby network client driver, there was a problem with result sets.  A new jar file, created to resolve this problem, is available for download.
 
However, I just looked at the SQuirreL site and the 2.0 final version has been released.  It's likely this release of SQuirreL has the fix for the problem with result sets.
 
Susan

acemccloudxx@comcast.net wrote:
Has anyone tried to use the SQirrel program with Derby?

Was it a success or a failure?



--0-609983840-1126029239=:69046--