Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 79861 invoked from network); 30 Mar 2007 14:21:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Mar 2007 14:21:10 -0000 Received: (qmail 14156 invoked by uid 500); 30 Mar 2007 14:21:10 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 14143 invoked by uid 500); 30 Mar 2007 14:21:10 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 14117 invoked by uid 99); 30 Mar 2007 14:21:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Mar 2007 07:21:09 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jeffgbutler@gmail.com designates 64.233.162.232 as permitted sender) Received: from [64.233.162.232] (HELO nz-out-0506.google.com) (64.233.162.232) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Mar 2007 07:21:01 -0700 Received: by nz-out-0506.google.com with SMTP id q3so441700nzb for ; Fri, 30 Mar 2007 07:20:41 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=qxMRlApIWqHvwXaWNlGiQv93gQ49lX1cjZ9Cn+O79hanSycGeVST/MVziTnz0In/yQzP/beQxhxiG/TTF7gwTBJb+sSs+FY88o3ouQnHe+pc0+ll0WoAYeDzVVFj9oj61svMayTxQwS/4Voi7akfanBNOfJiH1KuAa9WTY6PITc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=T+/b4Q9New2M/UcTE4o8RAI5cMrDbcmeGpk3kM25Lt5fc4XB05s9RDVahUqcavDyeeZshGizG4VdZUPx1Xiwlt1+0ppQfsz7UCVeZIWVgLGuvxSEmGQ8BINJmd3Xilu0CkuwVKVVvHf8LxlQoPUxfbPhG4pXm1ioCEl3gEyzy0Q= Received: by 10.114.174.2 with SMTP id w2mr748597wae.1175264440820; Fri, 30 Mar 2007 07:20:40 -0700 (PDT) Received: by 10.114.72.19 with HTTP; Fri, 30 Mar 2007 07:20:40 -0700 (PDT) Message-ID: Date: Fri, 30 Mar 2007 09:20:40 -0500 From: "Jeff Butler" To: user-java@ibatis.apache.org Subject: Re: Configurable static parameters in SQL In-Reply-To: <460D131D.6030703@fh-joanneum.at> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_46699_1667582.1175264440749" References: <437852.40488.qm@web60416.mail.yahoo.com> <460CF1A4.3070703@fh-joanneum.at> <460D131D.6030703@fh-joanneum.at> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_46699_1667582.1175264440749 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Ahh SQL Server...you vex me. Starting with SQL Server 2005, Microsoft has finally started using the proper terminology here (schema is the proper term, SQL Server called it "database owner" previously). Most databases allow you to set a default schema in the connection URL, but I'm not sure if SQL Server does or not. This is new territory for SQL Server. However, I know that you could create a database user and specify a default schema that way. Jeff Butler On 3/30/07, Ilya Boyandin wrote: > > Really? And how can I set it in the URL? > > I think, it's not the schema, but something different. It's "database > owner", something specific to MS SQL, I think. > > Ilya > > Jeff Butler wrote: > > If you are only needing to set the schema, then you could set a > > default schema on the JDBC connection URL and then avoid the use of > > schemas completely within your SQL. > > > > Jeff Butler > > > > > > ------=_Part_46699_1667582.1175264440749 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Ahh SQL Server...you vex me.
 
Starting with SQL Server 2005, Microsoft has finally started using the proper terminology here (schema is the proper term, SQL Server called it "database owner" previously).
 
Most databases allow you to set a default schema in the connection URL, but I'm not sure if SQL Server does or not.  This is new territory for SQL Server.  However, I know that you could create a database user and specify a default schema that way.
 
Jeff Butler

 
On 3/30/07, Ilya Boyandin <Ilya.Boyandin@fh-joanneum.at> wrote:
Really? And how can I set it in the URL?

I think, it's not the schema, but something different. It's "database
owner", something specific to MS SQL, I think.

Ilya

Jeff Butler wrote:
> If you are only needing to set the schema, then you could set a
> default schema on the JDBC connection URL and then avoid the use of
> schemas completely within your SQL.
>
> Jeff Butler
>
>


------=_Part_46699_1667582.1175264440749--