Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41F67C9B.50302@Mutagen.Net>
Date: Tue, 25 Jan 2005 09:06:35 -0800
From: Jack Klebanoff <klebanof@Mutagen.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: Re: JDBC spec question for ResultSet.updateObject method
References: <41F5FFFF.CF202E81@Remulak.Net>
In-Reply-To: <41F5FFFF.CF202E81@Remulak.Net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Mamta Satoor wrote:

>Hi,
>
>The JDBC API Tutorial and Reference book says that
>"The method setObject (on PreparedStatement) can take a null value only if
>the JDBC type is specified".
>But I couldn't find anything similar for ResultSet.updateObject(int columnIndex, Object x).
>Should this method throw an exception if null is passed for the Object since there is no
>way to specify JDBC type for this particular signature of updateObject?
>
>thanks,
>Mamta
>
>  
>
I suspect that a PreparedStatement may not always be able to decide on 
the type of a parameter when it compiles a statement, or it may not be 
able to do so easily. So PreparedStatement.setObject( i, null) may have 
trouble deciding how to handle the null. However a ResultSet knows the 
types of all of its columns, so ResultSet.updateObject( i, null) should 
treat the null as being of the type of the underlying column, which it 
knows.

Jack