Re: [api-dev] Possible bug with MySQL and OOo ResultSet

2009-10-30 Thread Sergio Corato
Alex Thurgood ha scritto: Hi Frank, Sergio, It would appear that the 3.51 ODBC driver only supports dynamic cursors in FORWARD_ONLY and STATIC modes if this page is correct : http://www.verbose.fr/mysql_5.0/mysql-connectors.html 25.1.14.2. Est-ce que MyODBC accepte les curseurs dynamiques?

Re: [api-dev] Possible bug with MySQL and OOo ResultSet

2009-10-29 Thread Frank Schoenheit, Sun Microsystems Germany
Hi Sergio, oStmt = oConn.createStatement() oStmt.setPropertyValue(ResultSetType, com.sun.star.sdbc.ResultSetType.SCROLL_INSENSITIVE) oStmt.setPropertyValue(ResultSetConcurrency, com.sun.star.sdbc.ResultSetConcurrency.READ_ONLY) oRs = oStmt.executeQuery(sql_string) oRs.next c =

Re: [api-dev] Possible bug with MySQL and OOo ResultSet

2009-10-29 Thread Alex Thurgood
Hi Frank, Sergio, It would appear that the 3.51 ODBC driver only supports dynamic cursors in FORWARD_ONLY and STATIC modes if this page is correct : http://www.verbose.fr/mysql_5.0/mysql-connectors.html 25.1.14.2. Est-ce que MyODBC accepte les curseurs dynamiques? Oui. MyODBC 3.51 supporte

[api-dev] Possible bug with MySQL and OOo ResultSet

2009-10-28 Thread Sergio Corato
I have this code: oStmt = oConn.createStatement() oStmt.setPropertyValue(ResultSetType, com.sun.star.sdbc.ResultSetType.SCROLL_INSENSITIVE) oStmt.setPropertyValue(ResultSetConcurrency, com.sun.star.sdbc.ResultSetConcurrency.READ_ONLY) oRs = oStmt.executeQuery(sql_string) oRs.next c =