Hello Marco
As soon as the tool is in beta I will send you a copy. I think it will
take 2/3 weeks.
If you need some test before the tool is available, send me the driver
and I'll test it.
Regards
Blas Rodriguez Somoza.
----- Original Message -----
From: "Paskamp, Marco" <[EMAIL PROTECTED]>
To: "'Blas Rodriguez Somoza'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, February 05, 2002 12:58 PM
Subject: RE: JDBC Test
> Hello,
>
> > -----Original Message-----
> > From: Blas Rodriguez Somoza [mailto:[EMAIL PROTECTED]]
> > Sent: Freitag, 1. Februar 2002 14:44
> > To: [EMAIL PROTECTED]
> > Cc: Paskamp, Marco
> > Subject: JDBC Test
> >
> > Some days ago, I ask if the JDBC Test Suite is a TODO for
> > the JDBC Driver, and Marco answers that it is.
> >
> > I'm working on a general JDBC manager/editor and I want
> > to test drivers without a J2EE server, so I'm preparing a
> > tool to do it.
> >
> > I begin implementing those tests included in the Test
> > Suite, because those are the official ones, excluding those
> > that check get/set of datatypes (9).
> >
> > I did the following tests, with the following results:
> >
> > 0.- Connection
> >
> > OK
> >
> > 1.- DatabaseMetaData
> >
> > getUDTs - Not Implemented (If the Driver does not
> > support it, it must return empty ResultSet)
> > getVersionColumns - Not Implemented (If the Driver
> > does not support it, it must return empty ResultSet)
>
> This is a known bug and already fixed in the next version of JDBC-driver.
>
> >
> > 2.- ResultSetMetaData
> >
> > OK
> >
> > 3.- Statement (excluding get/set checks related to types)
> >
> > Statement.executeQuery() that tries to insert a row
> > must throw SQLException
> > Statement.executeUpdate() that tries to select a row
> > from the table must throw SQLException
> > Statement.setFetchSize(negative) must throw SQLException.
> > Statement.setMaxFieldSize(negative) must throw SQLException.
> > Statement.setMaxRows(negative) must throw SQLException
> > Statement.setQueryTimeout(negative) must throw SQLException.
>
> Accepted, I will change it in the next version of the JDBC-driver.
>
> >
> > Statement.setMaxFieldSize() don't set the value.
> > Statement.setMaxRows() don't set the value.
>
> Why should anyone want to do this? But I will correct it in the next
version
> too.
>
> > 4.- PreparedStatement
> >
> > PreparedStatement.clearParameters() don't work.
> > PreparedStatement.execute() if the preparedStatement
> > has parameters and was not set must throw SQLException
> > PreparedStatement.executeUpdate() if the
> > preparedStatement has parameters and was not set must throw
> > SQLException.
> > PreparedStatement.executeQuery() if the
> > preparedStatement has parameters and was not set must throw
> > SQLException.
>
> I`m not sure if the JDBC-specification defines to throw an exception if a
> parameters was not set. At the moment the driver initialize these
parameters
> as null values. Should I change this behaviour and throw an exception?
Hints
> are welcome.
>
> > In a couple of days I'll send the remaining tests.
> > (ResultSet, exception, escapeSyntax, dateTime, batchUpdate)
>
> I`m very interesting in your test results. Maybe you can send me your test
> suite when you have finished developing it. So I can spare the time to
> implement these test cases too.
>
> Regards,
> Marco
> ----------------------------------------------
> Marco PASKAMP
> SAP DB, SAP Labs Berlin
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general
>
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
