https://issues.apache.org/ooo/show_bug.cgi?id=121837
Fred Toussi <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Fred Toussi <[email protected]> --- Hi All, Iam adding some short comments here on the CWS and current HSQLDB development. I will support AOO developers and QA testers with integration of new HSQLDB versions. I have looked at the AOO code and know to some extent what it is doing. It needs at least one, but preferably two or three developers to work on the AOO side. Pedro has made a good start and he should be encouraged to continue with the help of others. I was working on the HSQLDB side while Ocke Janssen was developing the CWS and OOo 3.4 in parallel. We were in regular contact. In April 2011, the final version of CWS was ready to be released with OOo 3.4, but (I think due to a push to get the 3.4 milestone release out) it was postponed to 3.5. We released HSQLDB 2.1 specifically to have an official release to be integrated in OOo. Patches to HSQLDB were included in CWS and applied to 2.1.0 before 2.2.0 came out with those changes integrated. Therefore the CWS sync point would be HSQLDB 2.2.0 and later (but excluding 2.2.9 which had some reported issues). You can simply place the HSQLDB 2.x jar in the jars directory and it works. No need to compile the jar. See this thread for some ongoing comments from testers. https://sourceforge.net/projects/hsqldb/forums/forum/73674/topic/5485246 Exactly because Base has not changed much from the OOo code, and the fact that CWS and the inherited OOo code were developed in synch, will make it easy to move to CWS. There are improvements in CWS which are possible only with HSQLDB 2.x. As Ariel commented, this change should happen in a branch and tested by QA volunteers before integration. The main technical difference between pre and post-CWS is the use of a different Java interface org.hsqldb.persist.RandomAccessInterface instead of org.hsqldb.lib.Storage. We developed this change to allow Base to make more intelligent choices about when to persist the changed data. Other differeces are due to improved SQL support in 2.x. Version 2.3.0 is gradually getting ready for release. We have released snapshot jars of this version, which are available here: http://www.hsqldb.org/repos/org/hsqldb/hsqldb/SNAPSHOT/ Since last year, I have tested the 2.3.0 code with LO and AOO code and improved the code. The last test was with the snapshot hsqldb-20130206.203335-33.jar. These tests are primarily to ensure interoperability with "mixed-mode" external file databases. I have not tested with CWS myself, but will start to do so in the future. Because the new HSQLDB has better logging options and the fact that persistence can be controlled better in OO with CWS with the new Java interface, it should be possible to avoid the ocassional crashes of the embedded database that users have complained about. One possible option is to warn the user when the maximum size of the database exceeds a limit. At the same time, this integration providss a easy way to use large mixed-mode external file databases with backup capabilities. After CWS integration, you can open the old databases in readonly mode (no alteration) or upgrade them to the new version. Some people have said they want to be able to modify the data in an old database without upgrading it. I intend to support this capability in a newer version after the release of 2.3.0. I would suggest to use the forum.openoffice.org to exchange information about the branch development, with separate threads used by developers and QA people to discuss issues. As the forum posts are editable, it is a better place for this task than Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
