Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 14533 invoked from network); 20 Mar 2007 23:08:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Mar 2007 23:08:11 -0000 Received: (qmail 38647 invoked by uid 500); 20 Mar 2007 23:08:18 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 38620 invoked by uid 500); 20 Mar 2007 23:08:18 -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 38611 invoked by uid 99); 20 Mar 2007 23:08:18 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Mar 2007 16:08:18 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [32.97.110.149] (HELO e31.co.us.ibm.com) (32.97.110.149) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Mar 2007 16:08:09 -0700 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e31.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l2KN7mEO002464 for ; Tue, 20 Mar 2007 19:07:48 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l2KN7m5n063666 for ; Tue, 20 Mar 2007 17:07:48 -0600 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l2KN7msi027414 for ; Tue, 20 Mar 2007 17:07:48 -0600 Received: from [127.0.0.1] (DMCSDJDT41P.usca.ibm.com [9.72.133.51]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l2KN7kUf027304 for ; Tue, 20 Mar 2007 17:07:48 -0600 Message-ID: <46006914.4090200@apache.org> Date: Tue, 20 Mar 2007 16:07:00 -0700 From: Daniel John Debrunner User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Collation implementation WAS Re: Should COLLATION attribute related code go in BasicDatabase? References: <45F6E90F.2090706@apache.org> <45F9620E.4050105@apache.org> <45F99873.2020305@sbcglobal.net> <460063D5.1060005@sbcglobal.net> In-Reply-To: <460063D5.1060005@sbcglobal.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Mike Matrigali wrote: > My opinion is that this work should be done in the datavalue factory and > not outside. Dan suggested at one point that some of the work of > generating classes/instances should move from Monitor to datavalue factory. > > So I was assuming something like RowUtil.newClassInfoTemplate instead > of calling Monitor.classFromIdentifier(format_ids[i]) get an array of > InstanceGetter's, it would call something like > datavaluefactory.classFromIdentifier(format_ids[i], collator_ids[i]) - > then every InstanceGetter would produce the right type with collator set > from then on. +1 Dan.