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 andreask1@vivodinet.gr
 designates 83.171.203.1 as permitted sender)
Message-ID: <48494A34.50103@vivodinet.gr>
Date: Fri, 06 Jun 2008 17:31:16 +0300
From: Andreas Kyrmegalos <andreask1@vivodinet.gr>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Database connection not bound to default database schema when
 authenticating through LDAP?
References: <484887F2.1020402@vivodinet.gr> <4848DD6A.7000200@sun.com>
 <4848E214.9010903@vivodinet.gr> <48493980.8070709@sun.com>
In-Reply-To: <48493980.8070709@sun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for taking the time to consider my question and posting such a 
lengthy reply Rick. Luckily, I have found a way to force a default 
schema for my project's hibernate mappings and get things going just 
like I want them to be. For now anyway. Thanks again.

Andreas

Rick Hillegas wrote:
> Hi Andreas,
>
> I can see that for many applications it would be useful to have a 
> concept of a database-wide default schema, that is, a schema that all 
> users start out in when they get a fresh connection. That is not the 
> way Derby works. For Derby, the default schema is user-specific, not 
> database-wide. This is true even in the degenerate case of an embedded 
> application which does not run with authentication turned on: in that 
> case the username defaults to APP and the default schema is APP's schema.
>
> The 2003 SQL standard does not offer any guidance on this topic. 
> According to part 2, section 4.37.2 (SQL-session identification), the 
> default schema of a session is vendor-defined.
>
> I don't remember any deep reason about why Derby has this default 
> behavior. It may be nothing more complicated than the fact that the 
> original programmers were familiar with this default from previous 
> databases which they had worked on.
>
> Some databases let you bind a default schema to a username. See for 
> instance http://msdn.microsoft.com/en-us/library/ms190387.aspx. I 
> think it would be straightforward to build such a mechanism for 
> Derby--although this would take you into session startup logic and the 
> devil could be in the details. I think there are plenty of people 
> around who understand that logic and who could coach a newcomer 
> through this project.
>
> In the meantime, the only workaround I see is for your application to 
> force the schema to a default value when your application hands out 
> connections.
>
> Please pardon me if I have talked past your real concern.
>
> Hope this helps,
> -Rick