db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From davi...@apache.org
Subject svn commit: r386169 [25/36] - in /db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master: DerbyNet/jdk16/ DerbyNetClient/jdk16/ jdk16/
Date Wed, 15 Mar 2006 21:31:59 GMT
Added: db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/jdk16/updatableResultSet.out
URL: http://svn.apache.org/viewcvs/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/jdk16/updatableResultSet.out?rev=386169&view=auto
==============================================================================
--- db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/jdk16/updatableResultSet.out (added)
+++ db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/jdk16/updatableResultSet.out Wed Mar 15 13:31:53 2006
@@ -0,0 +1,4830 @@
+Start testing delete and update using JDBC2.0 updateable resultset apis
+Negative Testl - request for scroll insensitive updatable resultset will give a read only scroll insensitive resultset
+WARNING 01X03: Insensitive updatable result sets are not supported by server; remapping to insensitive read-only cursor
+requested TYPE_SCROLL_INSENSITIVE, CONCUR_UPDATABLE but that is not supported
+Make sure that we got TYPE_SCROLL_INSENSITIVE? true
+Make sure that we got CONCUR_READ_ONLY? true
+ownDeletesAreVisible(ResultSet.TYPE_SCROLL_INSENSITIVE)? false
+othersDeletesAreVisible(ResultSet.TYPE_SCROLL_INSENSITIVE)? false
+deletesAreDetected(ResultSet.TYPE_SCROLL_INSENSITIVE)? false
+JDBC 2.0 updatable resultset api will fail on this resultset because this is not an updatable resultset
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Negative Test2 - request for scroll sensitive updatable resultset will give a read only scroll insensitive resultset
+WARNING 01X02: Scroll sensitive result sets are not supported by server; remapping to forward-only cursor
+requested TYPE_SCROLL_SENSITIVE, CONCUR_UPDATABLE but that is not supported
+Jira issue Derby-154 : When client connects to Network Server using JCC, it incorrectly shows support for scroll sensitive updatable resultsets
+Make sure that we got TYPE_SCROLL_INSENSITIVE? true
+Make sure that we got CONCUR_READ_ONLY? true
+JDBC 2.0 updatable resultset api will fail on this resultset because this is not an updatable resultset
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Negative Test3 - request a read only resultset and attempt deleteRow and updateRow on it
+Make sure that we got CONCUR_READ_ONLY? true
+Now attempting to send a deleteRow on a read only resultset.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Now attempting to send an updateRow on a read only resultset.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Negative Test4 - request a read only resultset and send a sql with FOR UPDATE clause and attempt deleteRow/updateRow on it
+Make sure that we got CONCUR_READ_ONLY? true
+Now attempting to send a deleteRow on a read only resultset with FOR UPDATE clause in the SELECT sql.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Now attempting to send a updateRow on a read only resultset with FOR UPDATE clause in the SELECT sql.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Negative Test5 - request resultset with no FOR UPDATE clause and CONCUR_READ_ONLY
+Make sure that we got CONCUR_READ_ONLY? true
+Now attempting to send a delete on a sql with no FOR UPDATE clause and CONCUR_READ_ONLY.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Now attempting to send a updateRow on a sql with no FOR UPDATE clause and CONCUR_READ_ONLY.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Negative Test6 - request updatable resultset for sql with FOR READ ONLY clause
+Make sure that we got CONCUR_READ_ONLY? true
+Jira issue Derby-159 : Warnings raised by Derby are not getting passed to the Client in Network Server Mode
+Will see the warnings in embedded mode only
+Now attempting to send a delete on a sql with FOR READ ONLY clause.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Now attempting to send a updateRow on a sql with FOR READ ONLY clause.
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Negative Test7 - attempt to deleteRow & updateRow on updatable resultset when the resultset is not positioned on a row
+Make sure that we got CONCUR_UPDATABLE? true
+Now attempt a deleteRow without first doing next on the resultset.
+SQL State : XCL08
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is not on a row. : 
+Now attempt a updateRow without first doing next on the resultset.
+updateRow will check if it is on a row or not even though no changes have been made to the row using updateXXX
+SQL State : null
+Got expected exception Invalid operation to update at current cursor position
+ResultSet is positioned after the last row. attempt to deleteRow at this point should fail!
+SQL State : XCL07
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is closed. Verify that autocommit is OFF. : 
+ResultSet is positioned after the last row. attempt to updateRow at this point should fail!
+SQL State : null
+Got expected exception Invalid operation to update at current cursor position
+Negative Test8 - attempt deleteRow & updateRow on updatable resultset after closing the resultset
+Make sure that we got CONCUR_UPDATABLE? true
+SQL State : null
+Got expected exception Invalid operation: result set closed
+SQL State : null
+Got expected exception Invalid operation: result set closed
+Negative Test9 - try updatable resultset on system table
+SQL State : 42Y90
+Got expected exception FOR UPDATE is not permitted in this type of statement.   : 
+Negative Test10 - try updatable resultset on a view
+SQL State : 42Y90
+Got expected exception FOR UPDATE is not permitted in this type of statement.   : 
+Negative Test11 - attempt to open updatable resultset when there is join in the select query should fail
+SQL State : 42Y90
+Got expected exception FOR UPDATE is not permitted in this type of statement.   : 
+Negative Test12 - With autocommit on, attempt to drop a table when there is an open updatable resultset on it
+Opened an updatable resultset. Now trying to drop that table through another Statement
+SQL State : X0X95
+Got expected exception Operation 'DROP TABLE' cannot be performed on object 'T1' because there is an open ResultSet dependent on that object. : 
+Since autocommit is on, the drop table exception resulted in a runtime rollback causing updatable resultset object to close
+SQL State : 24000
+Got expected exception Invalid cursor state - no current row. : 
+SQL State : 24000
+Got expected exception Invalid cursor state - no current row. : 
+Negative Test13 - foreign key constraint failure will cause deleteRow to fail
+SQL State : 23503
+Got expected exception DELETE on table 'TABLEWITHPRIMARYKEY' caused a violation of foreign key constraint 'FK' for key (1,1).  The statement has been rolled back. : 
+Since autocommit is on, the constraint exception resulted in a runtime rollback causing updatable resultset object to close
+Jira entry Derby-160 : for Network Server because next should have failed
+FAIL!!! next should have failed because foreign key constraint failure resulted in a runtime rollback
+Negative Test14 - foreign key constraint failure will cause updateRow to fail
+SQL State : 23503
+Got expected exception UPDATE on table 'TABLEWITHPRIMARYKEY' caused a violation of foreign key constraint 'FK' for key (1,1).  The statement has been rolled back. : 
+Since autocommit is on, the constraint exception resulted in a runtime rollback causing updatable resultset object to close
+Jira entry Derby-160 : for Network Server because next should have failed
+FAIL!!! next should have failed because foreign key constraint failure resulted in a runtime rollback
+Negative Test15 - Can't call updateXXX methods on columns that do not correspond to a column in the table
+SQL State : null
+Got expected exception Column not updatable
+Negative Test16 - Call updateXXX method on out of the range column
+There are only 2 columns in the select list and we are trying to send updateXXX on column position 3
+SQL State : null
+Got expected exception Invalid argument: parameter index 3 is out of range.
+Positive Test1a - request updatable resultset for forward only type resultset
+requested TYPE_FORWARD_ONLY, CONCUR_UPDATABLE
+got TYPE_FORWARD_ONLY? true
+got CONCUR_UPDATABLE? true
+JDBC 2.0 updatable resultset apis on this ResultSet object will pass because this is an updatable resultset
+column 1 on this row before deleteRow is 1
+column 2 on this row before deleteRow is aa                  
+Since after deleteRow(), in embedded mode and Network Server mode using Derby Net Client, ResultSet is positioned before the next row, getXXX will fail
+SQL State : null
+Got expected exception Invalid operation to read at current cursor position.
+calling deleteRow again w/o first positioning the ResultSet on the next row will fail
+SQL State : XCL08
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is not on a row. : 
+Position the ResultSet with next()
+Should be able to deletRow() on the current row now
+Positive Test1b - request updatable resultset for forward only type resultset
+column 1 on this row before updateInt is 1
+column 1 on this row after updateInt is 234
+column 2 on this row before updateString is aa                  
+now updateRow on the row
+Since after updateRow(), in embedded mode and Network Server mode using Derby Net Client, ResultSet is positioned before the next row, getXXX will fail
+SQL State : null
+Got expected exception Invalid operation to read at current cursor position.
+calling updateRow again w/o first positioning the ResultSet on the next row will fail
+SQL State : null
+Got expected exception Invalid operation to update at current cursor position
+Position the ResultSet with next()
+Should be able to updateRow() on the current row now
+Positive Test1c - use updatable resultset to do postitioned delete
+requested TYPE_FORWARD_ONLY, CONCUR_UPDATABLE
+got TYPE_FORWARD_ONLY? true
+got CONCUR_UPDATABLE? true
+column 1 on this row before positioned delete 234
+column 2 on this row before positioned delete aa                  
+column 1 on this deleted row is 234
+column 2 on this deleted row is aa                  
+doing positioned delete again w/o first positioning the ResultSet on the next row will fail
+SQL State : XCL08
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is not on a row. : 
+Position the ResultSet with next()
+Should be able to do positioned delete on the current row now
+Positive Test1d - updatable resultset to do positioned update
+column 1 on this row before positioned update is 1
+now dow positioned update on the row
+column 1 on the updated  row is 1
+column 1 on the updated  row is aa                  
+Refreshing the row
+SQL State : null
+Got expected exception This method should only be called on ResultSet objects that are scrollable(type TYPE_SCROLL_SENSITIVE or TYPE_SCROLL_INSENSITIVE)
+doing positioned update again w/o positioning the RS will succeed
+because the cursor is still positioned
+Position the ResultSet with next()
+Should still be able to do positioned update
+Positive Test2 - even if no columns from table specified in the column list, we should be able to get updatable resultset
+Will work in embedded mode because target table is not derived from the columns in the select list
+Will not work in network server mode because it derives the target table from the columns in the select list
+total number of rows in T1 
+	 1
+	 -
+	{3}
+column 1 on this row is 1
+SQL State : 42X01
+Got expected exception Syntax error: Encountered "WHERE" at line 1, column 14. : 
+total number of rows in T1 after one deleteRow is 
+	 1
+	 -
+	{3}
+Positive Test3a - use prepared statement with concur updatable status to test deleteRow
+requested TYPE_FORWARD_ONLY, CONCUR_UPDATABLE
+got TYPE_FORWARD_ONLY? true
+got CONCUR_UPDATABLE? true
+column 1 on this row is 1
+Since after deleteRow(), ResultSet is positioned before the next row, getXXX will fail
+SQL State : null
+Got expected exception Invalid operation to read at current cursor position.
+calling deleteRow again w/o first positioning the ResultSet on the next row will fail
+SQL State : XCL08
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is not on a row. : 
+Position the ResultSet with next()
+Should be able to deletRow() on the current row now
+Positive Test3b - use prepared statement with concur updatable status to test updateXXX
+requested TYPE_FORWARD_ONLY, CONCUR_UPDATABLE
+got TYPE_FORWARD_ONLY? true
+got CONCUR_UPDATABLE? true
+column 1 on this row is 1
+column 1 on this row after updateInt is 5
+Since after updateRow(), ResultSet is positioned before the next row, getXXX will fail
+SQL State : null
+Got expected exception Invalid operation to read at current cursor position.
+calling updateRow/updateXXX again w/o first positioning the ResultSet on the next row will fail
+SQL State : null
+Got expected exception Invalid operation to update at current cursor position
+SQL State : null
+Got expected exception Invalid operation to update at current cursor position
+SQL State : null
+Got expected exception Invalid operation at current cursor position.
+Position the ResultSet with next()
+Should be able to cancelRowUpdates() on the current row now
+Positive Test4 - use callable statement with concur updatable status
+requested TYPE_FORWARD_ONLY, CONCUR_UPDATABLE
+got TYPE_FORWARD_ONLY? true
+got CONCUR_UPDATABLE? true
+column 1 on this row is 1
+Since after deleteRow(), ResultSet is positioned before the next row, getXXX will fail
+SQL State : null
+Got expected exception Invalid operation to read at current cursor position.
+calling deleteRow again w/o first positioning the ResultSet on the next row will fail
+SQL State : XCL08
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is not on a row. : 
+Position the ResultSet with next()
+Should be able to deletRow() on the current row now
+Positive Test5 - donot have to select primary key to get an updatable resultset
+column 1 on this row is 1
+now try to delete row when primary key is not selected for that row
+Positive Test6a - For Forward Only resultsets, DatabaseMetaData will return false for ownDeletesAreVisible and deletesAreDetected
+This is because, after deleteRow, we position the ResultSet before the next row. We don't make a hole for the deleted row and then stay on that deleted hole
+ownDeletesAreVisible(ResultSet.TYPE_FORWARD_ONLY)? false
+othersDeletesAreVisible(ResultSet.TYPE_FORWARD_ONLY)? true
+deletesAreDetected(ResultSet.TYPE_FORWARD_ONLY)? false
+The JDBC program should look at rowDeleted only if deletesAreDetected returns true
+Since Derby returns false for detlesAreDetected for FORWARD_ONLY updatable resultset,the program should not rely on rs.rowDeleted() for FORWARD_ONLY updatable resultsets
+Have this call to rs.rowDeleted() just to make sure the method does always return false? false
+Have this call to rs.rowDeleted() just to make sure the method does always return false? false
+Positive Test6b - For Forward Only resultsets, DatabaseMetaData will return false for ownUpdatesAreVisible and updatesAreDetected
+This is because, after updateRow, we position the ResultSet before the next row
+ownUpdatesAreVisible(ResultSet.TYPE_FORWARD_ONLY)? false
+othersUpdatesAreVisible(ResultSet.TYPE_FORWARD_ONLY)? true
+updatesAreDetected(ResultSet.TYPE_FORWARD_ONLY)? false
+The JDBC program should look at rowUpdated only if updatesAreDetected returns true
+Since Derby returns false for updatesAreDetected for FORWARD_ONLY updatable resultset,the program should not rely on rs.rowUpdated() for FORWARD_ONLY updatable resultsets
+Have this call to rs.rowUpdated() just to make sure the method does always return false? false
+Have this call to rs.rowUpdated() just to make sure the method does always return false? false
+Positive Test7a - delete using updatable resultset api from a temporary table
+following rows in temp table before deleteRow
+	 C21,C22
+	 --- ---
+	{21,1}
+	{22,1}
+As expected, no rows in temp table after deleteRow
+	 C21,C22
+	 --- ---
+Positive Test7b - update using updatable resultset api from a temporary table
+following rows in temp table before deleteRow
+	 C31,C32
+	 --- ---
+	{21,1}
+	{22,1}
+As expected, updated rows in temp table after updateRow
+	 C31,C32
+	 --- ---
+	{123,1}
+	{123,1}
+Positive Test8a - change the name of the statement when the resultset is open and see if deleteRow still works
+This test works in embedded mode since Derby can handle the change in the name of the statement with an open resultset
+But it fails under Network Server mode because JCC and Derby Net Client do not allow statement name change when there an open resultset against it
+change the cursor name(case sensitive name) with setCursorName and then try to deleteRow
+change the cursor name one more time with setCursorName and then try to deleteRow
+SQL State : null
+Got expected exception Invalid operation: setCursorName() called when there are open ResultSet's on the Statement.
+Positive Test8b - change the name of the statement when the resultset is open and see if updateRow still works
+This test works in embedded mode since Derby can handle the change in the name of the statement with an open resultset
+But it fails under Network Server mode because JCC and Derby Net Client do not allow statement name change when there an open resultset against it
+change the cursor name one more time with setCursorName and then try to updateRow
+change the cursor name(case sensitive name) with setCursorName and then try to updateRow
+SQL State : null
+Got expected exception Invalid operation: setCursorName() called when there are open ResultSet's on the Statement.
+Positive Test9a - using correlation name for the table in the select sql works in embedded mode and Network Server using Derby Net Client driver
+Correlation name for table does not work in Network Server mode (using JCC) because the drivers construct the delete sql with the correlation name rather than the base table name
+column 1 on this row is 1
+now try to deleteRow
+PASS!!! passed in embedded mode
+Positive Test9b - using correlation name for updatable columns is not allowed.
+Table t1 has following rows
+	 C1,C2
+	 -- --
+	{1,aa                  }
+	{2,bb                  }
+	{3,cc                  }
+attempt to get an updatable resultset using correlation name for an updatable column
+The sql is SELECT c1 as col1, c2 as col2 FROM t1 abcde FOR UPDATE of c1
+SQL State : 42X42
+Got expected exception Correlation name not allowed for column 'C1' because it is part of the FOR UPDATE list. : 
+attempt to get an updatable resultset using correlation name for an readonly column. It should work
+The sql is SELECT c1, c2 as col2 FROM t1 abcde FOR UPDATE of c1
+Table t1 after updateRow has following rows
+	 C1,C2
+	 -- --
+	{11,aa                  }
+	{2,bb                  }
+	{3,cc                  }
+Positive Test9c - try to updateXXX on a readonly column. Should get error
+SQL State : null
+Got expected exception Column not updatable
+attempt to get an updatable resultset using correlation name for an readonly column. It should work
+The sql is SELECT c1, c2 as col2 FROM t1 abcde FOR UPDATE of c1
+Table t1 after updateRow has following rows
+	 C1,C2
+	 -- --
+	{11,aa                  }
+	{2,bb                  }
+	{3,cc                  }
+Positive Test9d - try to updateXXX on a readonly column with correlation name. Should get error
+SQL State : null
+Got expected exception Column not updatable
+Table t1 has following rows
+	 C1,C2
+	 -- --
+	{1,aa                  }
+	{2,bb                  }
+	{3,cc                  }
+Positive Test10 - 2 updatable resultsets going against the same table, will they conflict?
+delete using first resultset
+attempt to send deleteRow on the same row through a different resultset should throw an exception
+SQL State : XCL08
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is not on a row. : 
+Move to next row in the 2nd resultset and then delete using the second resultset
+Positive Test11 - setting the fetch size to > 1 will be ignored by updatable resultset. Same as updatable cursors
+Notice the Fetch Size in run time statistics output.
+1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            
                                    
+-----
+Statement Name: 
+	<xxx-cursor-name-xxx>
+Statement Text: 
+	SELECT * FROM t1 FOR UPDATE of c1
+Parse Time: 0
+Bind Time: 0
+Optimize Time: 0
+Generate Time: 0
+Compile Time: 0
+Execute Time: 0
+Begin Compilation Timestamp : null
+End Compilation Timestamp : null
+Begin Execution Timestamp : null
+End Execution Timestamp : null
+Statement Execution Plan Text: 
+Table Scan ResultSet for T1 at read committed isolation level using exclusive row locking chosen by the optimizer
+Number of opens = 1
+Rows seen = 0
+Rows filtered = 0
+Fetch Size = 1
+	constructor time (milliseconds) = 0
+	open time (milliseconds) = 0
+	next time (milliseconds) = 0
+	close time (milliseconds) = 0
+scan information: 
+	Bit set of columns fetched=All
+	Number of columns fetched=2
+	Number of pages visited=0
+	Number of rows qualified=0
+	Number of rows visited=0
+	Scan type=heap
+	start position: 
+null	stop position: 
+null	qualifiers:
+None
+statement's fetch size is 200
+Positive Test12a - make sure delete trigger gets fired when deleteRow is issued
+Verify that before delete trigger got fired, row count is 0 in deleteTriggerInsertIntoThisTable
+	 1
+	 -
+	{0}
+column 1 on this row is 1
+now try to delete row and make sure that trigger got fired
+Verify that delete trigger got fired by verifying the row count to be 1 in deleteTriggerInsertIntoThisTable
+	 1
+	 -
+	{1}
+Positive Test12b - make sure update trigger gets fired when updateRow is issued
+Verify that before update trigger got fired, row count is 0 in updateTriggerInsertIntoThisTable
+	 1
+	 -
+	{0}
+column 1 on this row is 1
+now try to update row and make sure that trigger got fired
+Verify that update trigger got fired by verifying the row count to be 1 in updateTriggerInsertIntoThisTable
+	 1
+	 -
+	{1}
+Positive Test13a - Another test case for delete trigger
+column 1 on this row is 1
+this delete row will fire the delete trigger which will delete all the rows from the table and from the resultset
+SQL State : XCL07
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is closed. Verify that autocommit is OFF. : 
+Verify that delete trigger got fired by verifying the row count to be 0 in table1WithTriggers
+	 1
+	 -
+	{0}
+Positive Test13b - Another test case for update trigger
+Look at the current contents of table2WithTriggers
+	 C1,C2
+	 -- --
+	{1,1}
+	{2,2}
+	{3,3}
+	{4,4}
+column 1 on this row is 2
+this update row will fire the update trigger which will update all the rows in the table to have c1=1 and hence no more rows will qualify for the resultset
+SQL State : null
+Got expected exception Invalid operation to update at current cursor position
+Verify that update trigger got fired by verifying that all column c1s have value 1 in table2WithTriggers
+	 C1,C2
+	 -- --
+	{1,1}
+	{1,2}
+	{1,3}
+	{1,4}
+Positive Test14a - make sure self referential delete cascade works when deleteRow is issued
+	 C1,C2
+	 -- --
+	{e1,null}
+	{e2,e1}
+	{e3,e2}
+	{e4,e3}
+column 1 on this row is e1
+this delete row will cause the delete cascade constraint to delete all the rows from the table and from the resultset
+SQL State : XCL07
+Got expected exception Cursor '<xxx-cursor-name-xxx>' is closed. Verify that autocommit is OFF. : 
+Verify that delete trigger got fired by verifying the row count to be 0 in selfReferencingT1
+	 1
+	 -
+	{0}
+Positive Test14b - make sure self referential update restrict works when updateRow is issued
+	 C1,C2
+	 -- --
+	{e1,null}
+	{e2,e1}
+	{e3,e2}
+	{e4,e3}
+column 1 on this row is e1
+update row should fail because cascade constraint is update restrict
+SQL State : 23503
+Got expected exception UPDATE on table 'SELFREFERENCINGT2' caused a violation of foreign key constraint 'MANAGES2' for key (e1).  The statement has been rolled back. : 
+Positive Test15 - With autocommit off, attempt to drop a table when there is an open updatable resultset on it
+Opened an updatable resultset. Now trying to drop that table through another Statement
+SQL State : X0X95
+Got expected exception Operation 'DROP TABLE' cannot be performed on object 'T1' because there is an open ResultSet dependent on that object. : 
+Since autocommit is off, the drop table exception will NOT result in a runtime rollback and hence updatable resultset object is still open
+Positive Test16a - Do deleteRow within a transaction and then rollback the transaction
+Verify that before delete trigger got fired, row count is 0 in deleteTriggerInsertIntoThisTable
+	 1
+	 -
+	{0}
+Verify that before deleteRow, row count is 4 in table0WithTriggers
+	 1
+	 -
+	{4}
+column 1 on this row is 1
+now try to delete row and make sure that trigger got fired
+Verify that delete trigger got fired by verifying the row count to be 1 in deleteTriggerInsertIntoThisTable
+	 1
+	 -
+	{1}
+Verify that deleteRow in transaction, row count is 3 in table0WithTriggers
+	 1
+	 -
+	{3}
+Verify that after rollback, row count is back to 0 in deleteTriggerInsertIntoThisTable
+	 1
+	 -
+	{0}
+Verify that after rollback, row count is back to 4 in table0WithTriggers
+	 1
+	 -
+	{4}
+Positive Test16b - Do updateRow within a transaction and then rollback the transaction
+Verify that before update trigger got fired, row count is 0 in updateTriggerInsertIntoThisTable
+	 1
+	 -
+	{0}
+Look at the data in table0WithTriggers before trigger gets fired
+	 C1,C2
+	 -- --
+	{1,1}
+	{2,2}
+	{3,3}
+	{4,4}
+column 1 on this row is 1
+now try to update row and make sure that trigger got fired
+Verify that update trigger got fired by verifying the row count to be 1 in updateTriggerInsertIntoThisTable
+	 1
+	 -
+	{1}
+Verify that new data in table0WithTriggers
+	 C1,C2
+	 -- --
+	{123,1}
+	{2,2}
+	{3,3}
+	{4,4}
+Verify that after rollback, row count is back to 0 in updateTriggerInsertIntoThisTable
+	 1
+	 -
+	{0}
+Verify that after rollback, table0WithTriggers is back to its original contents
+	 C1,C2
+	 -- --
+	{1,1}
+	{2,2}
+	{3,3}
+	{4,4}
+Positive Test17 - After deleteRow, resultset is positioned before the next row
+getXXX right after deleteRow will fail because resultset is not positioned on a row, instead it is right before the next row
+SQL State : null
+Got expected exception Invalid operation to read at current cursor position.
+Positive Test18 - Test cancelRowUpdates method as the first updatable ResultSet api on a read-only resultset
+SQL State : null
+Got expected exception This method cannot be invoked while the cursor is on the insert row or if this ResultSet object has a concurrency of CONCUR_READ_ONLY.
+Positive Test19 - Test updateRow method as the first updatable ResultSet api on a read-only resultset
+  Got expected exception : This method cannot be invoked while the cursor is on the insert row or if the concurrency of this ResultSet object is CONCUR_READ_ONLY.
+Positive Test20 - Test updateXXX methods as the first updatable ResultSet api on a read-only resultset
+  Test updateShort on a readonly resultset
+  Using column position as first parameter to updateShort
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateShort
+  Got expected exception : ResultSet is not updatable.
+  Test updateInt on a readonly resultset
+  Using column position as first parameter to updateInt
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateInt
+  Got expected exception : ResultSet is not updatable.
+  Test updateLong on a readonly resultset
+  Using column position as first parameter to updateLong
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateLong
+  Got expected exception : ResultSet is not updatable.
+  Test updateBigDecimal on a readonly resultset
+  Using column position as first parameter to updateBigDecimal
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateBigDecimal
+  Got expected exception : ResultSet is not updatable.
+  Test updateFloat on a readonly resultset
+  Using column position as first parameter to updateFloat
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateFloat
+  Got expected exception : ResultSet is not updatable.
+  Test updateDouble on a readonly resultset
+  Using column position as first parameter to updateDouble
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateDouble
+  Got expected exception : ResultSet is not updatable.
+  Test updateString on a readonly resultset
+  Using column position as first parameter to updateString
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateString
+  Got expected exception : ResultSet is not updatable.
+  Test updateAsciiStream on a readonly resultset
+  Using column position as first parameter to updateAsciiStream
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateAsciiStream
+  Got expected exception : ResultSet is not updatable.
+  Test updateCharacterStream on a readonly resultset
+  Using column position as first parameter to updateCharacterStream
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateCharacterStream
+  Got expected exception : ResultSet is not updatable.
+  Test updateByte on a readonly resultset
+  Using column position as first parameter to updateByte
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateByte
+  Got expected exception : ResultSet is not updatable.
+  Test updateBytes on a readonly resultset
+  Using column position as first parameter to updateBytes
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateBytes
+  Got expected exception : ResultSet is not updatable.
+  Test updateBinaryStream on a readonly resultset
+  Using column position as first parameter to updateBinaryStream
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateBinaryStream
+  Got expected exception : ResultSet is not updatable.
+  Test updateClob on a readonly resultset
+  Using column position as first parameter to updateClob
+  Got expected exception : JDBC 3 method called - not yet supported
+  Using column name as first parameter to updateClob
+  Got expected exception : JDBC 3 method called - not yet supported
+  Test updateDate on a readonly resultset
+  Using column position as first parameter to updateDate
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateDate
+  Got expected exception : ResultSet is not updatable.
+  Test updateTime on a readonly resultset
+  Using column position as first parameter to updateTime
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateTime
+  Got expected exception : ResultSet is not updatable.
+  Test updateTimestamp on a readonly resultset
+  Using column position as first parameter to updateTimestamp
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateTimestamp
+  Got expected exception : ResultSet is not updatable.
+  Test updateBlob on a readonly resultset
+  Using column position as first parameter to updateBlob
+  Got expected exception : JDBC 3 method called - not yet supported
+  Using column name as first parameter to updateBlob
+  Got expected exception : JDBC 3 method called - not yet supported
+  Test updateBoolean on a readonly resultset
+  Using column position as first parameter to updateBoolean
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateBoolean
+  Got expected exception : ResultSet is not updatable.
+  Test updateNull on a readonly resultset
+  Using column position as first parameter to updateNull
+  Got expected exception : ResultSet is not updatable.
+  Using column name as first parameter to updateNull
+  Got expected exception : ResultSet is not updatable.
+  Test updateArray on a readonly resultset
+  Using column position as first parameter to updateArray
+  Got expected exception : JDBC 3 method called - not yet supported
+  Using column name as first parameter to updateArray
+  Got expected exception : JDBC 3 method called - not yet supported
+  Test updateRef on a readonly resultset
+  Using column position as first parameter to updateRef
+  Got expected exception : JDBC 3 method called - not yet supported
+  Using column name as first parameter to updateRef
+  Got expected exception : JDBC 3 method called - not yet supported
+Positive Test21 - Test all updateXXX(excluding updateObject) methods on all the supported sql datatypes
+Next datatype to test is SMALLINT
+  Testing updateShort on SQL type SMALLINT
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type SMALLINT
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type SMALLINT
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type SMALLINT
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type SMALLINT
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type SMALLINT
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type SMALLINT
+    Using column position as first parameter to updateString
+      Got expected exception : Invalid data conversion: Parameter instance 1992                                                         is invalid for requested conversion.
+    Using column name as first parameter to updateString
+      Got expected exception : Invalid data conversion: Parameter instance 1992                                                         is invalid for requested conversion.
+  Testing updateAsciiStream on SQL type SMALLINT
+    Using column position as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+  Testing updateCharacterStream on SQL type SMALLINT
+    Using column position as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+  Testing updateByte on SQL type SMALLINT
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type SMALLINT
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type SMALLINT
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type SMALLINT
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type SMALLINT
+    Using column position as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+  Testing updateTime on SQL type SMALLINT
+    Using column position as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+  Testing updateTimestamp on SQL type SMALLINT
+    Using column position as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+  Testing updateBlob on SQL type SMALLINT
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type SMALLINT
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type SMALLINT
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type SMALLINT
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type SMALLINT
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is INTEGER
+  Testing updateShort on SQL type INTEGER
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type INTEGER
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type INTEGER
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type INTEGER
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type INTEGER
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type INTEGER
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type INTEGER
+    Using column position as first parameter to updateString
+      Got expected exception : Invalid data conversion: Parameter instance 1992                                                         is invalid for requested conversion.
+    Using column name as first parameter to updateString
+      Got expected exception : Invalid data conversion: Parameter instance 1992                                                         is invalid for requested conversion.
+  Testing updateAsciiStream on SQL type INTEGER
+    Using column position as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+  Testing updateCharacterStream on SQL type INTEGER
+    Using column position as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+  Testing updateByte on SQL type INTEGER
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type INTEGER
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type INTEGER
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type INTEGER
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type INTEGER
+    Using column position as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+  Testing updateTime on SQL type INTEGER
+    Using column position as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+  Testing updateTimestamp on SQL type INTEGER
+    Using column position as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+  Testing updateBlob on SQL type INTEGER
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type INTEGER
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type INTEGER
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type INTEGER
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type INTEGER
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is BIGINT
+  Testing updateShort on SQL type BIGINT
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type BIGINT
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type BIGINT
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type BIGINT
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type BIGINT
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type BIGINT
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type BIGINT
+    Using column position as first parameter to updateString
+      Got expected exception : Invalid data conversion: Parameter instance 1992                                                         is invalid for requested conversion.
+    Using column name as first parameter to updateString
+      Got expected exception : Invalid data conversion: Parameter instance 1992                                                         is invalid for requested conversion.
+  Testing updateAsciiStream on SQL type BIGINT
+    Using column position as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+  Testing updateCharacterStream on SQL type BIGINT
+    Using column position as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+  Testing updateByte on SQL type BIGINT
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type BIGINT
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type BIGINT
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type BIGINT
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type BIGINT
+    Using column position as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+  Testing updateTime on SQL type BIGINT
+    Using column position as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+  Testing updateTimestamp on SQL type BIGINT
+    Using column position as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+  Testing updateBlob on SQL type BIGINT
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type BIGINT
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type BIGINT
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type BIGINT
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type BIGINT
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is DECIMAL(10,5)
+  Testing updateShort on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateString
+      Got expected exception : Invalid data conversion: Parameter instance 1992                                                         is invalid for requested conversion.
+    Using column name as first parameter to updateString
+      Got expected exception : Invalid data conversion: Parameter instance 1992                                                         is invalid for requested conversion.
+  Testing updateAsciiStream on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+  Testing updateCharacterStream on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+  Testing updateByte on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+  Testing updateTime on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+  Testing updateTimestamp on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+  Testing updateBlob on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type DECIMAL(10,5)
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is REAL
+  Testing updateShort on SQL type REAL
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type REAL
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type REAL
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type REAL
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type REAL
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type REAL
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type REAL
+    Using column position as first parameter to updateString
+    Using column name as first parameter to updateString
+  Testing updateAsciiStream on SQL type REAL
+    Using column position as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+  Testing updateCharacterStream on SQL type REAL
+    Using column position as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+  Testing updateByte on SQL type REAL
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type REAL
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type REAL
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type REAL
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type REAL
+    Using column position as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+  Testing updateTime on SQL type REAL
+    Using column position as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+  Testing updateTimestamp on SQL type REAL
+    Using column position as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+  Testing updateBlob on SQL type REAL
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type REAL
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type REAL
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type REAL
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type REAL
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is DOUBLE
+  Testing updateShort on SQL type DOUBLE
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type DOUBLE
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type DOUBLE
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type DOUBLE
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type DOUBLE
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type DOUBLE
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type DOUBLE
+    Using column position as first parameter to updateString
+    Using column name as first parameter to updateString
+  Testing updateAsciiStream on SQL type DOUBLE
+    Using column position as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+  Testing updateCharacterStream on SQL type DOUBLE
+    Using column position as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+  Testing updateByte on SQL type DOUBLE
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type DOUBLE
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type DOUBLE
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type DOUBLE
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type DOUBLE
+    Using column position as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+  Testing updateTime on SQL type DOUBLE
+    Using column position as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+  Testing updateTimestamp on SQL type DOUBLE
+    Using column position as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+  Testing updateBlob on SQL type DOUBLE
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type DOUBLE
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type DOUBLE
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type DOUBLE
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type DOUBLE
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is CHAR(60)
+  Testing updateShort on SQL type CHAR(60)
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type CHAR(60)
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type CHAR(60)
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type CHAR(60)
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type CHAR(60)
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type CHAR(60)
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type CHAR(60)
+    Using column position as first parameter to updateString
+    Using column name as first parameter to updateString
+  Testing updateAsciiStream on SQL type CHAR(60)
+    Using column position as first parameter to updateAsciiStream
+    Using column name as first parameter to updateAsciiStream
+  Testing updateCharacterStream on SQL type CHAR(60)
+    Using column position as first parameter to updateCharacterStream
+    Using column name as first parameter to updateCharacterStream
+  Testing updateByte on SQL type CHAR(60)
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type CHAR(60)
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type CHAR(60)
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type CHAR(60)
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type CHAR(60)
+    Using column position as first parameter to updateDate
+    Using column name as first parameter to updateDate
+  Testing updateTime on SQL type CHAR(60)
+    Using column position as first parameter to updateTime
+    Using column name as first parameter to updateTime
+  Testing updateTimestamp on SQL type CHAR(60)
+    Using column position as first parameter to updateTimestamp
+    Using column name as first parameter to updateTimestamp
+  Testing updateBlob on SQL type CHAR(60)
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type CHAR(60)
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type CHAR(60)
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type CHAR(60)
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type CHAR(60)
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is VARCHAR(60)
+  Testing updateShort on SQL type VARCHAR(60)
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type VARCHAR(60)
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type VARCHAR(60)
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type VARCHAR(60)
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type VARCHAR(60)
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type VARCHAR(60)
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type VARCHAR(60)
+    Using column position as first parameter to updateString
+    Using column name as first parameter to updateString
+  Testing updateAsciiStream on SQL type VARCHAR(60)
+    Using column position as first parameter to updateAsciiStream
+    Using column name as first parameter to updateAsciiStream
+  Testing updateCharacterStream on SQL type VARCHAR(60)
+    Using column position as first parameter to updateCharacterStream
+    Using column name as first parameter to updateCharacterStream
+  Testing updateByte on SQL type VARCHAR(60)
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type VARCHAR(60)
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type VARCHAR(60)
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type VARCHAR(60)
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type VARCHAR(60)
+    Using column position as first parameter to updateDate
+    Using column name as first parameter to updateDate
+  Testing updateTime on SQL type VARCHAR(60)
+    Using column position as first parameter to updateTime
+    Using column name as first parameter to updateTime
+  Testing updateTimestamp on SQL type VARCHAR(60)
+    Using column position as first parameter to updateTimestamp
+    Using column name as first parameter to updateTimestamp
+  Testing updateBlob on SQL type VARCHAR(60)
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type VARCHAR(60)
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type VARCHAR(60)
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type VARCHAR(60)
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type VARCHAR(60)
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is LONG VARCHAR
+  Testing updateShort on SQL type LONG VARCHAR
+    Using column position as first parameter to updateShort
+    Using column name as first parameter to updateShort
+  Testing updateInt on SQL type LONG VARCHAR
+    Using column position as first parameter to updateInt
+    Using column name as first parameter to updateInt
+  Testing updateLong on SQL type LONG VARCHAR
+    Using column position as first parameter to updateLong
+    Using column name as first parameter to updateLong
+  Testing updateBigDecimal on SQL type LONG VARCHAR
+    Using column position as first parameter to updateBigDecimal
+    Using column name as first parameter to updateBigDecimal
+  Testing updateFloat on SQL type LONG VARCHAR
+    Using column position as first parameter to updateFloat
+    Using column name as first parameter to updateFloat
+  Testing updateDouble on SQL type LONG VARCHAR
+    Using column position as first parameter to updateDouble
+    Using column name as first parameter to updateDouble
+  Testing updateString on SQL type LONG VARCHAR
+    Using column position as first parameter to updateString
+    Using column name as first parameter to updateString
+  Testing updateAsciiStream on SQL type LONG VARCHAR
+    Using column position as first parameter to updateAsciiStream
+    Using column name as first parameter to updateAsciiStream
+  Testing updateCharacterStream on SQL type LONG VARCHAR
+    Using column position as first parameter to updateCharacterStream
+    Using column name as first parameter to updateCharacterStream
+  Testing updateByte on SQL type LONG VARCHAR
+    Using column position as first parameter to updateByte
+    Using column name as first parameter to updateByte
+  Testing updateBytes on SQL type LONG VARCHAR
+    Using column position as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBytes
+      Got expected exception : Illegal Conversion
+  Testing updateBinaryStream on SQL type LONG VARCHAR
+    Using column position as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBinaryStream
+      Got expected exception : Illegal Conversion
+  Testing updateClob on SQL type LONG VARCHAR
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type LONG VARCHAR
+    Using column position as first parameter to updateDate
+    Using column name as first parameter to updateDate
+  Testing updateTime on SQL type LONG VARCHAR
+    Using column position as first parameter to updateTime
+    Using column name as first parameter to updateTime
+  Testing updateTimestamp on SQL type LONG VARCHAR
+    Using column position as first parameter to updateTimestamp
+    Using column name as first parameter to updateTimestamp
+  Testing updateBlob on SQL type LONG VARCHAR
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type LONG VARCHAR
+    Using column position as first parameter to updateBoolean
+    Using column name as first parameter to updateBoolean
+  Testing updateNull on SQL type LONG VARCHAR
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type LONG VARCHAR
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type LONG VARCHAR
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is CHAR(2) FOR BIT DATA
+  Testing updateShort on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateShort
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateShort
+      Got expected exception : Illegal Conversion
+  Testing updateInt on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateInt
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateInt
+      Got expected exception : Illegal Conversion
+  Testing updateLong on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateLong
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateLong
+      Got expected exception : Illegal Conversion
+  Testing updateBigDecimal on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBigDecimal
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBigDecimal
+      Got expected exception : Illegal Conversion
+  Testing updateFloat on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateFloat
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateFloat
+      Got expected exception : Illegal Conversion
+  Testing updateDouble on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateDouble
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDouble
+      Got expected exception : Illegal Conversion
+  Testing updateString on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateString
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateString
+      Got expected exception : Illegal Conversion
+  Testing updateAsciiStream on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+  Testing updateCharacterStream on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+  Testing updateByte on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateByte
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateByte
+      Got expected exception : Illegal Conversion
+  Testing updateBytes on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBytes
+    Using column name as first parameter to updateBytes
+  Testing updateBinaryStream on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBinaryStream
+    Using column name as first parameter to updateBinaryStream
+  Testing updateClob on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+  Testing updateTime on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+  Testing updateTimestamp on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+  Testing updateBlob on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBoolean
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBoolean
+      Got expected exception : Illegal Conversion
+  Testing updateNull on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateArray
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateRef on SQL type CHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateRef
+      Got expected exception : JDBC 3 method called - not yet supported
+Next datatype to test is VARCHAR(2) FOR BIT DATA
+  Testing updateShort on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateShort
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateShort
+      Got expected exception : Illegal Conversion
+  Testing updateInt on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateInt
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateInt
+      Got expected exception : Illegal Conversion
+  Testing updateLong on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateLong
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateLong
+      Got expected exception : Illegal Conversion
+  Testing updateBigDecimal on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBigDecimal
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBigDecimal
+      Got expected exception : Illegal Conversion
+  Testing updateFloat on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateFloat
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateFloat
+      Got expected exception : Illegal Conversion
+  Testing updateDouble on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateDouble
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDouble
+      Got expected exception : Illegal Conversion
+  Testing updateString on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateString
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateString
+      Got expected exception : Illegal Conversion
+  Testing updateAsciiStream on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateAsciiStream
+      Got expected exception : Illegal Conversion
+  Testing updateCharacterStream on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateCharacterStream
+      Got expected exception : Illegal Conversion
+  Testing updateByte on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateByte
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateByte
+      Got expected exception : Illegal Conversion
+  Testing updateBytes on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBytes
+    Using column name as first parameter to updateBytes
+  Testing updateBinaryStream on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBinaryStream
+    Using column name as first parameter to updateBinaryStream
+  Testing updateClob on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateClob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateDate on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateDate
+      Got expected exception : Illegal Conversion
+  Testing updateTime on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTime
+      Got expected exception : Illegal Conversion
+  Testing updateTimestamp on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateTimestamp
+      Got expected exception : Illegal Conversion
+  Testing updateBlob on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+    Using column name as first parameter to updateBlob
+      Got expected exception : JDBC 3 method called - not yet supported
+  Testing updateBoolean on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateBoolean
+      Got expected exception : Illegal Conversion
+    Using column name as first parameter to updateBoolean
+      Got expected exception : Illegal Conversion
+  Testing updateNull on SQL type VARCHAR(2) FOR BIT DATA
+    Using column position as first parameter to updateNull
+    Using column name as first parameter to updateNull
+  Testing updateArray on SQL type VARCHAR(2) FOR BIT DATA

[... 3255 lines stripped ...]


Mime
View raw message