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] Sun Oct 25 00:11:36 +0000 2009 ------- ==> atj Hello Drew. well, you are right, users may have requested the One-Key-less-procedures. It depends, whether the onwer of the application is accepting it or not. No serious appliaction is using autocommit, as an unintentional commit will make roll-back neccessary that just causes pain to everybody, like multi-use environments, key-generating transactions etc. Think about bookkeeping, invoicing etc. However, you can judge yourself. Think about developing a DBMS, and think about which feature can miss, whithout the need to prevent the application from dataloss by unintentional commit, the keyhit-saving autocommit or the one-key-more(which in not really the case). A roll-back is needed for both, but in case of explicit commit the user knows why. So it depends on what comes first in regard to data-integrity, auto or not auto. regarding the BORG-calendar. It is not my favorite application, the calendar has some disadvantages, however, it has a good potential. And it is not the only HSQL-based application, that can be useful together with OO.o. It is a cann't be, that OO.o is not save for use external HSQL-Sources. I am not that much familiar with stuff like that, but I tried to find the differences, and it looks as OO.o is tempering the properties-file and the storage-type in there. BORG hold tables in memory, OO.o hold it cached. So Borg has data available immidiatly. OO.o not, but could make the data immidiatly available, for example by clearing cache when waiting on next input, or just stop this rather useless feature. that would not have any impact on performance in single-user or SOHO-environments, but is the much saver concept. Well, I think you got what I ment, keep it safe, keep it simple, just the old-school-way. Martin P.S.: No, I do not want to discuss this in UX. I hate mailing-lists, stuff needs to be centralized, thats enough. And I do not see the neccessity for this issue. This is a defect-by-design, but nevertheless a defect. --------------------------------------------------------------------- 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]
