Re: JDBC 2.0 conformance, documentation and todo list

My guess is that is is a setup problem.  I get a success for this test.

--Barry


********************************************************************************
Beginning Test:  testAllProceduresAreCallable
********************************************************************************
SVR: Using DataSource
SVR: intTabSize: 5
SVR: intTabTypeSize: 5
SVR: createString1: create table ctstable1 (TYPE_ID int, TYPE_DESC
varchar(32), primary key(TYPE_ID))
SVR: createString: create table ctstable2 (KEY_ID int, COF_NAME
varchar(32), PRICE float, TYPE_ID int, primary key(KEY_ID), foreign
key(TYPE_ID) references ctstable1)
SVR: Created the tables ctstable1 and ctstable2
SVR: Calling allProceduresAreCallable on DatabaseMetaData
SVR: allProceduresAreCallable method called by the current user
SVR: Removed the tables ctstable1 and ctstable2
SVR: Closed the database connection
SVR: Cleanup ok;
SVR: Test running in ejb vehicle passed
Test:  testAllProceduresAreCallable returned from running in ejb vehicle
********************************************************************************
End Test:  testAllProceduresAreCallable...........PASSED
********************************************************************************





Rene Pijlman wrote:
> On Wed, 08 Aug 2001 09:50:11 -0700, you wrote:
>
>>Have your run the JDBC conformance tests to help generate this
>>information?
>>
>
> Yes, I have run the test (1.2.1 EE version) and looked at some
> of the results. This will take more time, since there are
> hundreds of messages and it isn't always easy to find out what's
> going on.
>
> Unfortunately, I'm getting many failed results with messages
> like this:
>
> ********************************************************************************
> Beginning Test:  testAllProceduresAreCallable
> ********************************************************************************
> Using DataSource
> ERROR: SQL Exception : No suitable driver
> Calling allProceduresAreCallable on DatabaseMetaData
> ERROR: Unexpected exception null
> ERROR: Call to allProceduresAreCallable is Failed!
> ERROR: java.lang.NullPointerException
>
> And I'm quite sure this code in DatabaseMetaData isn't causing
> the problem :-)
>
>   public boolean allProceduresAreCallable() throws SQLException
>   {
>     return true;
>   }
>
>
>>There was a post a few days ago from one of the RedHat
>>engineers saying they had run it and were going to summarize the results
>>and post back to the list.  (I haven't yet seen that followup).
>>
>
> Would be good to here from them.
>
>
>>I ran the tests myself over the weekend, but haven't sorted
>>through the results either.
>>
>
> Could you do a quick grep for the message quoted above? I'd
> really like to know if this is caused by a problem in my
> setup... thanks.
>
>
>>Rene Pijlman wrote:
>>
>>>I've created a web page that aims to document the level of
>>>conformance of the JDBC driver to the JDBC 2.0 API. It also aims
>>>to document any deviations from the JDBC standard that have been
>>>found.
>>>http://lab.applinet.nl/postgresql-jdbc/
>>>
>
> Regards,
> René Pijlman
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
>