Hi Rick,
You need to make sure that the various metadata methods correctly report supporting of Boolean (getTypeInfo, for example) so suggested jdbcapi/metadata.java
For instance in the procedure 'getpc' in that test all datatypes are listed; you should probably add boolean in.
Also, I found 1 old boolean datatype specific test - I'm checking that we can still contribute that test based on the original approval from IBM.
Myrna
Myrna
On 8/10/05, Rick Hillegas <[EMAIL PROTECTED]> 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?
>
>
>
>
>
>
