Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 3106 invoked from network); 22 Jul 2005 08:04:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jul 2005 08:04:24 -0000 Received: (qmail 78985 invoked by uid 500); 22 Jul 2005 08:04:23 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 78966 invoked by uid 99); 22 Jul 2005 08:04:23 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jul 2005 01:04:23 -0700 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=SPF_HELO_FAIL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.110.131] (HELO e33.co.us.ibm.com) (32.97.110.131) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jul 2005 01:04:16 -0700 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e33.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j6M84JRu585828 for ; Fri, 22 Jul 2005 04:04:19 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j6M84IAH241068 for ; Fri, 22 Jul 2005 02:04:18 -0600 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j6M84ILq012489 for ; Fri, 22 Jul 2005 02:04:18 -0600 Received: from [127.0.0.1] (sig-9-48-115-52.mts.ibm.com [9.48.115.52]) by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j6M84DIH012415 for ; Fri, 22 Jul 2005 02:04:17 -0600 Message-ID: <42E0A87C.8050906@debrunners.com> Date: Fri, 22 Jul 2005 01:04:12 -0700 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jdo-dev@db.apache.org Subject: Re: Binding a char to PreparedStatement References: <003e01c58dd4$1437c6b0$0302a8c0@jpox> In-Reply-To: X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Craig Russell wrote: > Hi Erik, > > On Jul 21, 2005, at 2:10 AM, erik@jpox.org wrote: > >> CHAR(1) will not allow Unicode storage, you need either to use NCHAR(1), >> CHAR(4) or another type that allows you to store 2 bytes. > > > Correct. The point is what should be the default. Well, implementation defined really. Derby defines CHAR(1) as storage for one *character*, not one byte, character is really the intent of the SQL spec. Derby always uses Unicode as the character set, so CHAR(1) can store any Unicode character from Java. Dan.