Could you post the SELECT that you have executed to create the result set, and the definition of the table (to get what the key columns are)? Also, you should tell us what you mean with 'strange' results.
Regards Alexander Schröder SAP DB, SAP Labs Berlin -----Original Message----- From: Robert Klemme [mailto:[EMAIL PROTECTED] Sent: Dienstag, 17. Januar 2006 14:22 To: maxdb Subject: JDBC: Updatable ResultSet - expected behavior? Hi, I do an update on a table via a ResultSet. I noticed that this leads to strange results if I create the statement like this: tx.createStatement( ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE ) If I do it like this, all is fine: tx.createStatement( ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE ) There is no other user accessing the table. I'm not sure about a pattern here but it seems as if the first case has problems if there are multiple lines with similar entries. Is this expected behavior? Is this a bug? robert Driver Version: Manifest-Version: 1.0 Created-By: Apache Ant 1.5 Main-Class: com.sap.dbtech.jdbc.DriverSapDB Name: com/sap/dbtech/jdbc/ Specification-Title: Java Platform API Specification Specification-Version: 1.3.0 Specification-Vendor: Sun Microsystems, Inc. Implementation-Title: MaxDB JDBC Driver Implementation-Version: 7.6.0 Build 000-000-003-034 Implementation-Vendor: MySQL MaxDB Name: com/sap/dbtech/jdbcext/JDBCRowSetSapDB.class Java-Bean: True MaxDB Version: Name CR Version 7.5.00.18 Operating System Windows 2000 (WIN32) -- Have a look: http://www.flickr.com/photos/fussel-foto/ -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
