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: domain of gcaddu-derby-user@m.gmane.org
 designates 80.91.229.12 as permitted sender)
To: derby-user@db.apache.org
From: SET <nmset@netcourrier.com>
Subject: Re: Database-side programming
Date: Mon, 19 Jul 2010 08:56:07 +0000 (UTC)
Lines: 32
Message-ID: <loom.20100719T104622-129@post.gmane.org>
References: <201007181815.08998.nmset@netcourrier.com>
 <4C44059B.7080807@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)

Kristian Waagan <kristian.waagan@...> writes:

> 
> On 18.07.10 18:15, Saleem EDAH-TALLY wrote:
> > Hello,
> >
> > This concerns getting information from 'inside' Derby through JAVA code
called
> > by a procedure.
> >
> > The nested connection can be obtained with jdbc:default:connection. However
> > the URL attributes cannot be retrieved in any way.
> 
> Hi,
> 
> Maybe it would help if you tell why you want to do this, so people can 
> suggest a different mechanism if appropriate?
...
...

>From a stored procedure, I have to open a connection to another database.
The main unknown is the ssl mode parameter with the client driver. This parameter
is meaningless in embedded mode.
I could not find a way to determine this parameter from a stored procedure.
There is the derby.drda.sslMode property which can be retrieved from a
NetworkServerControl instance, but I could not find a way to access the current
instance.

CURRENT_USER does give the desired parameter.

Thank you for your reply.