Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 84883 invoked from network); 30 Apr 2007 19:05:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Apr 2007 19:05:17 -0000 Received: (qmail 44211 invoked by uid 500); 30 Apr 2007 19:05:24 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 43993 invoked by uid 500); 30 Apr 2007 19:05:23 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 43984 invoked by uid 99); 30 Apr 2007 19:05:23 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2007 12:05:23 -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.249 as permitted sender) Received: from [209.85.132.249] (HELO an-out-0708.google.com) (209.85.132.249) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2007 12:05:16 -0700 Received: by an-out-0708.google.com with SMTP id c25so1309673ana for ; Mon, 30 Apr 2007 12:04:55 -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=FYQNmugJlnLVl03LTybZZRCutKbu6hOk9H+BEkQx3UXgboE5MXbGyX4jLaPRxp+jtzxOGJ/v/7gfEO4izl2cef3ni08Y1igvLsNRzAZJsii4a0a9/70aAO95YHfIls5W2lXZFmxIkFo4LEObefiH9faxEcyPGYFrZbdMvD3mjQs= 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=aOq5AwfnH1LmYLVbuhyPNkzIEE8U0oPnH2gV8ltf2e9v6Wj5QEnQKuF5pO/gEud9ZFhp2pDBIAgVNwj7jMWZQX0QszPY1933Lt+93CgGpANkxSyAn2kTOf40NtPVoICIS51g/mQVANRRh2iPqoPCR7aVrq2Qf56idaNs2z3ksGM= Received: by 10.100.130.8 with SMTP id c8mr403017and.1177959879557; Mon, 30 Apr 2007 12:04:39 -0700 (PDT) Received: by 10.100.189.9 with HTTP; Mon, 30 Apr 2007 12:04:39 -0700 (PDT) Message-ID: Date: Mon, 30 Apr 2007 12:04:39 -0700 From: "Mamta Satoor" To: derby-dev@db.apache.org, mikem_app@sbcglobal.net Subject: Re: DERBY-1478 Lineitem DERBY-2599: Associating correct collation type and derivation with DTD In-Reply-To: <46363B78.8050304@sbcglobal.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_53894_33346550.1177959879469" References: <46363B78.8050304@sbcglobal.net> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_53894_33346550.1177959879469 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Yes, I have some work done in my codeline. I will post that partial change to DERBY-2599. thanks, Mamta On 4/30/07, Mike Matrigali wrote: > > > > Mamta Satoor wrote: > > Hi, > > > > I am working on putting the correct collation type and derivation for > > DTDs. The approach I am taking is to change all the constructors for > > DTDs to accept the collation type and derivation. It will be the > > responsibility of the caller of the DTD constructor to pass this > > information for all different kinds of DTDs, ie whether the DTD is for > > collation sensitive datatypes (which include the character string > > datatypes), or all the other non-collation sensitive datatypes (eg > > numeric, binary etc,). For non collation sensitive datatypes, the caller > > will pass collation derivation of "none" which will mean that collation > > type of such datatypes should be ignored. > > > > I just wanted to bring it to community's attention that this approach of > > changing the DTD constructor signature is requiring lot of changes since > > all the callers now have to taken on the task of passing the collation > > type and derivation. I think that is the right approach ie have callers > > take on the responsibility of associating the collation types and > > derivations for their DTDs. Let me know if anyone has any feedback on > > how I am approaching this. > > > Have you done any of this work yet, if so could you post a partial patch > as an example of the kinds of changes you are proposing. I don't expect > a completed work, just something to get a feel of the type of changes. > > > thanks, > > Mamta > > ------=_Part_53894_33346550.1177959879469 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Yes, I have some work done in my codeline. I will post that partial change to DERBY-2599.
 
thanks,
Mamta

 
On 4/30/07, Mike Matrigali <mikem_app@sbcglobal.net> wrote:


Mamta Satoor wrote:
> Hi,
>
> I am working on putting the correct collation type and derivation for
> DTDs. The approach I am taking is to change all the constructors for
> DTDs to accept the collation type and derivation. It will be the
> responsibility of the caller of the DTD constructor to pass this
> information for all different kinds of DTDs, ie whether the DTD is for
> collation sensitive datatypes (which include the character string
> datatypes), or all the other non-collation sensitive datatypes (eg
> numeric, binary etc,). For non collation sensitive datatypes, the caller
> will pass collation derivation of "none" which will mean that collation
> type of such datatypes should be ignored.
>
> I just wanted to bring it to community's attention that this approach of
> changing the DTD constructor signature is requiring lot of changes since
> all the callers now have to taken on the task of passing the collation
> type and derivation. I think that is the right approach ie have callers
> take on the responsibility of associating the collation types and
> derivations for their DTDs. Let me know if anyone has any feedback on
> how I am approaching this.
>
Have you done any of this work yet, if so could you post a partial patch
as an example of the kinds of changes you are proposing.  I don't expect
a completed work, just something to get a feel of the type of changes.

> thanks,
> Mamta


------=_Part_53894_33346550.1177959879469--