To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=36231
------- Additional comments from mhath...@openoffice.org Thu Oct 8 18:52:54 +0000 2009 ------- ==>fs hm I did not understood what two different items you are looking for, as the HSQL has no "primanota-concept" for delayed transactions. Isn't it, that the HSQLDB (back-end - if you wish) could be set to auto-execution of statements or not? COMMIT is one of those. so, at actual 1. You changed the behavior of forms 2. the method setautocommit is still unused While there had been a chance to substitute the lack of the missing 2. by using a working cycle-function within forms, even that isn't working anymore. I am sure you knew that, so I wonder about your question. However, as the HSQL is working in OOo like in a black box - everything is under the hood - you may start to make the properties available - or even give reliable infos how to hack/set it up manually. Note - substantial for dealing with OOo and data: when it is not possible to set the table-properties so that data will be updated by a manually controlled (explicit!) commit only, in forms aswell as in tableview - at least for me, OOo will never ever get the chance to be used for anything serious. Martin P.S.: look at the OP - this issue will make the 5-years-anniversery these days. --------------------------------------------------------------------- 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
