To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=36231
User atjensen changed the following:
What |Old value |New value
================================================================================
CC|'eberlein' |'atjensen,eberlein'
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Sat Oct 24 18:41:34
+0000 2009 -------
@mahatheoo -Before getting to the real question here:
"Autocommitting is a nasty nonsense-feature, invented by developers,"
Sorry but that statement is just wrong. Users, in certain contexts, expect it
and demand it - back office 10 key operations is a prime example, make them hit
one more key then absolutely necessary and your application is out the door and
in the dumper. (mistakes in keying are caught during a reconciliation step,
almost always, not during data input as it has proven to reduce overall
efficiency when keying in large numbers of transactions...but that is old school
stuff I suppose and often involves use of temp tables during data entry)
"everything seems to be left in default state. And it looks,
that OO.o is also setting foreign property-files back to default-state. This for
example might be the reason, why I can not use the HSQL-based BORG-calendar as
datasource, having it opend in OO.o will make it crash in BORG."
Well, I had to give that a try after reading the issue here. Using OO.o 3.1.1 or
3.2m_1 (dev build) and connecting to the BORG database using
jdbc:hsqldb:file:<path>\BORG_ allows me to have both applications open
simultaneously (using Ubuntu 9.04 here). I can enter data via SQL commands from
Base but not via the GUI, I can build forms but only against queries, not
tables, same with Reports and a few other oddities, but no crashes on either
side. The data entered in either is not available to the other applications
however until the connections have been closed and opened again. (I note that
BORG now ships with a MySQL schema as an option) However, as I am not a BORG
*smile*, user, If you want to pursue this I would be happy to work with you via
an OO.o mailing list or web forum or the BORG mailing list, where I see you
opened a thread on just this issue. We might find solutions...might be fun
actually, and perhaps we could contribute back to the BORG project any changes
needed to make it fully compatible with Base (OO.o).
---back to the question in this issue--
How should Base handle auto-commit? Should it be the default?
Any chance we could have this conversation on the mailing list versus the issue,
one, I hate this text box...and two - maybe we invite the UX team to get
involved...
---------------------------------------------------------------------
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]
