Return-Path: 
 <derby-dev-return-43800-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 24348 invoked from network); 5 Jun 2007 05:26:02 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 5 Jun 2007 05:26:02 -0000
Received: (qmail 10384 invoked by uid 500); 5 Jun 2007 05:26:05 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 10188 invoked by uid 500); 5 Jun 2007 05:26:05 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 10178 invoked by uid 99); 5 Jun 2007 05:26:05 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2007 22:26:05 -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 msatoor@gmail.com designates
 209.85.132.246 as permitted sender)
Received: from [209.85.132.246] (HELO an-out-0708.google.com) (209.85.132.246)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2007 22:26:00 -0700
Received: by an-out-0708.google.com with SMTP id c8so398848ana
        for <derby-dev@db.apache.org>; Mon, 04 Jun 2007 22:25:39 -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=LNifxoi7MBYXotFVn6mUXobhLbp1wPre8CNB0Uz4cmVifVag+k+6L6gmd7ecj25+u16Q2uKMmkRzh2Uha2R55KXmw6x45xtYEstUyXQ+DO68w0x+9LEP6QVTPNm3vSkNXdosZETSRfrMJVpW0ZNWqcOuDnkR4FAFZV2+/9R0vrk=
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=e1jZhgLr/b2yQRokBlsr6iQk3u93EXRTXXStS7oL4Sxu0uVlJaeDa1X7IxbpVVVeQhy+Qb8FtTUvo3gYMuls9Jqrqp/7tzw2iJ/eKnTjUmn9NowRhTjErfAJpi3uyMRS0Jg+DDENB2ffO19NxnH5dyxSeB/UcheIC+4Ac4aojS0=
Received: by 10.100.199.12 with SMTP id w12mr2996099anf.1181021139812;
        Mon, 04 Jun 2007 22:25:39 -0700 (PDT)
Received: by 10.100.194.14 with HTTP; Mon, 4 Jun 2007 22:25:39 -0700 (PDT)
Message-ID: <d9619e4a0706042225r19b04b48kaf94b44da42195d2@mail.gmail.com>
Date: Mon, 4 Jun 2007 22:25:39 -0700
From: "Mamta Satoor" <msatoor@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: Collation and parameter markers (?)
In-Reply-To: <466432A8.5030804@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_15119_19683631.1181021139770"
References: <466432A8.5030804@apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_15119_19683631.1181021139770
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Dan asked
****************************************************************************************
  "8)JDBC parameters (ie. ?) where the type of the parameter is a
character type will have the same collation as of the character set of
the schema where the statement is prepared. The collation derivation
will be implicit."

http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478

This seems wrong to me, is there some section of the SQL standard that
is being followed?

****************************************************************************************

Dan, this came from the Collation feature discussion thread below.
http://www.nabble.com/Collation-feature-discussion-tf3418026.html#a9743522

Basically, we followed SQL spec section 6.1 <data *type*> Syntax Rule
*3b*and 16.

Mamta

------=_Part_15119_19683631.1181021139770
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Dan asked</div>
<div>****************************************************************************************</div>
<div>&nbsp; &quot;8)JDBC parameters (ie. ?) where the type of the parameter is a<br>character type will have the same collation as of the character set of<br>the schema where the statement is prepared. The collation derivation
<br>will be implicit.&quot;<br><br><a href="http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478">http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478</a><br><br>This seems wrong to me, is there some section of the SQL standard that
<br>is being followed?<br>
<div><span class="gmail_quote">
<div>****************************************************************************************</div>
<div>&nbsp;</div>
<div>Dan, this came from the Collation feature discussion thread below.</div></span></div>
<div><a href="http://www.nabble.com/Collation-feature-discussion-tf3418026.html#a9743522">http://www.nabble.com/Collation-feature-discussion-tf3418026.html#a9743522</a></div>
<div>&nbsp;</div>
<div>Basically, we followed SQL spec section 6.1 &lt;data <b class="highlight">type</b>&gt; Syntax Rule&nbsp;<span><b class="highlight">3b</b> and 16.</span></div>
<div><span></span>&nbsp;</div>
<div><span>Mamta</span></div></div>
<div><br><br>&nbsp;</div>

------=_Part_15119_19683631.1181021139770--