Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of dremesh@gmail.com designates
 64.233.162.196 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=FJ/+AnT2Q+i/qD50d6QGKjhsoQrA4iW5D2vn01wuk2z1g9Zbxl9p6d10viAvr/7v2quczwnzDPaHllfBjOeIjE6dl99dyyyH/JHBvJeI9idNL2NH5T3KK+0Tpjv+IzYnxFU7OwTQgUI+NSXBZLpNNvYHhoupdrAMXX3OSjI6tqI=
Message-ID: <58ed70f505092109015606ec25@mail.gmail.com>
Date: Wed, 21 Sep 2005 09:01:06 -0700
From: Deepa Remesh <dremesh@gmail.com>
Reply-To: Deepa Remesh <dremesh@gmail.com>
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [jira] Updated: (DERBY-374) Invalid URL with Derby Client when
 connecting to Network Server causes protocol exception.
In-Reply-To: <43303A4D.9050906@sbcglobal.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <468024357.1127142629464.JavaMail.jira@ajax.apache.org>
	 <432EF50E.7070008@sbcglobal.net> <432F129D.7070400@sbcglobal.net>
	 <58ed70f505092009143e77b951@mail.gmail.com>
	 <43303A4D.9050906@sbcglobal.net>

On 9/20/05, Kathey Marsden <kmarsdenderby@sbcglobal.net> wrote:

> I think that is the best we can do from the server side as we cannot
> send a full SQLCARD in this case.
> I am not sure what message the client reports when this is returned by
> the server. If it does not seem informative enough, we could always add
> additional checking to the client to have it made clear and make the
> message match the embedded driver.  But I think you are right in taking
> the first step of fixing the NPE in the server and returning RDBAFLRM
> when the server cannot make a connection.
>

I am doing the following. In network server, check if a null
connection is returned by InternalDriver. If so, throw "new
SQLException("No suitable driver","08001");" to match behaviour with
embedded driver. The server will use this SQLException to build
RDBAFLRM and SQLCARD and send it to client.

When using embedded driver, this exception gets thrown by
DriverManager.getConnection method.

Output in ij:

//Embedded
ij> connect 'jdbc:derby:/sample:create=3Dtrue;';
ERROR 08001: No suitable driver

//Network Server with Derby Client
ij> connect 'jdbc:derby://localhost:1527/sample:create=3Dtrue;';
ERROR 08001: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08001, SQLERRMC:
No suitable driver

Please let me know if there are any comments.

Thanks,
Deepa