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 [email protected] Wed Aug 19 13:53:16 +0000 2009 ------- >fs well, I see that the changes to HSQL 1.9 will cause some problems, although as I understood these changes seems to be more under the hood and not that much relevant to applications calling HSQL-functions by skripts. However, I am not that much a developer to judge about that. But nevertheless I can not really accept your responds. I have in mind, that an OO-form should not be leavable by using any auto-commit-function, but only by using an explicit function. Of course this needs to think about locking etc, but this is related to OO.o only, as it is part of the form-properties, not related to HSQL. Example: Supposed you will have a record-copy-function sometimes (choose a record - dublicate it to temp - edit it - and start the base-table-updated when all is done from user-side) you will face the same problems. So you have the following options: Give up and wait until this feature is implemented in HSQL (which may not come!), implement it as an OO-base feature, or trust, that users will find a makro-solution. You understand, that it is not about your ambitions to solve this matter, it is about the competence within the community aswell as the willing of your employee to spend something on that. Thats all. Martin --------------------------------------------------------------------- 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: [email protected] For additional commands, e-mail: [email protected]
