Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (herse.apache.org: 32.97.110.149 is neither permitted
 nor denied by domain of qozinx@gmail.com)
Message-ID: <4612A517.9050103@gmail.com>
Date: Tue, 03 Apr 2007 12:03:51 -0700
From: Army <qozinx@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7.1) Gecko/20040707
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: some comments on collation wiki page
References: <4611F2C0.2040306@sbcglobal.net> <46126750.1010401@apache.org>
 <d9619e4a0704030839o48d9b41cs72c89518c70efc7c@mail.gmail.com>
 <46128C67.9080606@gmail.com> <461290D5.20602@gmail.com>
 <461299CA.9080903@apache.org> <46129CB4.9020306@gmail.com>
 <4612A0FA.9020601@apache.org>
In-Reply-To: <4612A0FA.9020601@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Daniel John Debrunner wrote:
> 
> I don't see how when the current schema is defined makes a difference as 
> to if they run without error or not? How does the current schema being a 
> user schema or a system schema make this statement compile to an error?
> 
>>    // Default schema APP.
>>
>>    PreparedStatement ps = conn.prepareStatement(
>>        "select tablename, tabletype from sys.systables where " +
>>        "CAST (tablename as varchar(128)) = ?"); 
> 

Okay, you are of course correct.  I somehow got it in my head that the collation 
of the CAST was determined at execution time, but that's not at all true. 
Nothing on the wiki indicates that, it was just a weird conclusion I jumped to 
for some reason.

Apologies for the noise.  Mamta, please feel free to disregard my comment and go 
ahead with your plans to set JDBC param character set at prepare time (which is 
the way that makes sense).

Sorry again,
Army