[dba-issues] [Issue 109328] Statements must been clos ed after calling a Stored Porcedure in MySQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109328 --- Additional comments from s...@openoffice.org Mon Feb 22 08:18:18 + 2010 --- @Drew OK but if we need to do that also with a PreparedStatement ? and later (when thins works) also with a preparedcall ? It makes the prepare things useless no ? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 109328] Statements must been clos ed after calling a Stored Porcedure in MySQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109328 User atjensen changed the following: What|Old value |New value CC|'sos' |'atjensen,sos' - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 109328] Statements must been clos ed after calling a Stored Porcedure in MySQL
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109328 --- Additional comments from atjen...@openoffice.org Sun Feb 21 16:48:27 + 2010 --- @sos what you describe is true, but I'm not at all sure this is a defect. The requirment to close your server side cursors is TTBOMK required. having to do so explicitly is IMO the norm (Basic Python Java), although in some environments, particular web based tools this requirement may be handled by a library and you may not explicitly have to manage this. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 109328] Statements must been clos ed after calling a Stored Porcedure in MySQL
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=109328
Issue #|109328
Summary|Statements must been closed after calling a Stored Por
|cedure in MySQL
Component|Database access
Version|1.0.0
Platform|PC
URL|
OS/Version|Windows XP
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P3
Subcomponent|none
Assigned to|dbaneedsconfirm
Reported by|sos
--- Additional comments from s...@openoffice.org Tue Feb 16 12:45:07 +
2010 ---
Using MySQL natice connector
trye this code
SUB TESTstoredprocedurecall
oBaseContext = CreateUnoService(com.sun.star.sdb.DatabaseContext)
oDB = oBaseContext.getByName(mysql_native)
oCon = oDB.getConnection(user, Password)
oStatement = oCon.createStatement()
sSQL1 = call teststoredprocedure('Parm1', '¨Parm2') ' must been pased in
right order
ostatement.execute(sSQL1)' gives True
oResultset1 = ostatement.getresultset
oResultSet1.next
print oResultset1.getstring(1)' confirmes the selection based on parameters
ostatement.close ' must been done otherwise we ran in a
Exception:'sdbc.SQLExepetion Commands out of sync, you can not run this
command now
'after this exception you need to restart OO or dispose oDB
ocon.close ' just to be sure everyting isclosed
end sub
this Exception Commands out of sync, you can not run this command now make
the use of PreparedStatements useless
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
