I think we want to make sure these tests pass with the network client as
well as with the embedded client...
David
Rick Hillegas wrote:
Hi Kathey,
I have found two tests which look like they monitor datatype
conformity for PreparedStatements and ResultSets:
jdbcapi/parameterMapping.java
jdbcapi/resultSet.java
BOOLEAN support was removed from these tests and I intend to put it
back in. This will verify that you can use jdbc to set BOOLEAN
parameters and retrieve BOOLEAN columns.
Are there other jdbc tests which I should amend? What other client
behavior should I track down?
Thanks,
-Rick
Kathey Marsden wrote:
Rick Hillegas wrote:
I propose to close bug 499 by re-enabling the ANSI-SQL standard
BOOLEAN datatype which was disabled before IBM open-sourced Derby.
A yes vote means that you want to re-enable the ANSI-SQL standard
BOOLEAN datatype.
A no vote means that you do NOT want Derby to support the ANSI-SQL
standard BOOLEAN datatype.
Please cast your vote by 5:00 pm Pacific time Thursday August 11.
What will the client behaviour be?
begin:vcard
fn:David Van Couvering
n:Van Couvering;David
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
