Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <434EFD77.2040303@sbcglobal.net>
Date: Thu, 13 Oct 2005 17:36:07 -0700
From: Army <qozinx@sbcglobal.net>
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 Development <derby-dev@db.apache.org>
Subject: setNull() using Types.VARCHAR for a CLOB parameter fails in embedded
 mode.
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

If I attempt to call PreparedStatement.setNull() and specify Types.VARCHAR when 
the actual parameter type (as determined at bind time) is CLOB, Derby in 
embedded mode will throw an error, while Derby in client/server mode will succeed.

Ex. running the following code:

	st.execute("create table t1 (c clob)");
	PreparedStatement pSt = conn.prepareStatement(
		"insert into t1 values (?)");
	try {
		pSt.setNull(1, Types.VARCHAR);
		pSt.execute();
		System.out.println("Error did NOT reproduce.");
	} catch (SQLException se) {
		System.out.println("Error reproduced:");
		se.printStackTrace();
	}

Against Derby embedded, the result will be:

   Error reproduced:
   SQL Exception: An attempt was made to get a data value of type 'CLOB' from a 
data value of type 'VARCHAR'.

But against the Network Server, everything works fine.  Derby embedded will work 
in other cases where compatible types are used (ex. using setNull() with 
Types.INTEGER for a BIGINT parameter), but fails for this particular situation. 
Thus I'm assuming this is _not_ intentional (i.e. that the above code should work).

Can anyone confirm one way or the other?  If I don't hear otherwise, I'll file a 
Jira issue tomorrow.

Thanks,
Army