Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

HSQLJAR 2.2.9 and OpenOffice

Help
2012-07-28
2014-01-19
1 2 > >> (Page 1 of 2)
  • Fred:

    On the other forum, you said:

    Fred
    I have just released another release candidate jar for HSQLDB
    version 2.2.9.

    http://www.hsqldb.org/repos/org/hsqldb/hsqldb/SNAPSHOT/

    This jar is designed to replace the hsqldb.jar (version 1.8.0) that is
    included with OpenOffice.org, LibreOffice and ApacheOpenOffice.

    Just to let you know my 'experience'. It would appear, that, things are not quite copacetic with OpenOffice 3.3.0 ( this is NOT AOO 3.4 . . . but . . . what many are using ) and the latest snapshot hsqldb.jar release candidate 2.2.9  ( hsqldb-2020728.163827-13.jar ).

    While it did convert the database to 2.2.9 this was an old 1.8.0.10 Embedded database . . . each VIEW worked exactly as expected ( returning the rows inside OpenOffice ). But, ALL TABLES, only 'displayed' ONE ROW . . . always the FIRST ROW in the table, but, not the rest ( additional rows ).

    I have found this to be true with prior releases of HSQLDB Version 2.2.9 and do NOT know if the issue is an OpenOffice issue, or, an issue with HSQLDB. Furthermore, I used the converted HSQLDB files, against SQLTool.jar, and, all the data is available.

    A few other concerns, with the 'conversion. In the converted database directory when using an OpenOffice Embedded database ( sorry, just had to mention this ) . . . a backup file in the database is NOT present ( as was true in the original hsql version 1.8.0.10 OpenOffice jar ). With ZIP file corruption, this, unfortunately should not happen, in my opinion. Put another way, I think an Embedded Open Office database should always include a backup file,

    Slideurle

     
  • Fred Toussi
    Fred Toussi
    2012-07-28

    Thanks. You have found a problem which I will investigate. I have tried several databases, and have seen a few tables with multiple rows. But as these were not made by myself, I don't know how many rows they are supposed to contain. Please supply a database which I can check.

    Regarding the .backup, this is now done in a different way  by default (see SET FILES INCREMENT BACKUP TRUE in the Guide).  This is the default for normal HSQLDB use (outside OO) and is safe. I will check and see if the previous method should be the default.

     
  • Fred:

    You said:

    Please supply a database which I can check.

    I would be happy to . . . but . . . forgive me, where should I send the OpenOffice .odb file ( which email address ) . . . and . . . do you want it 'converted' to 2.2.9 RC2 . . . or . . . the file with 1.8.0.10 . . . or . . . both?

    Yes, I did see / know about the SET FILES INCREMENT BACKUP TRUE default with 2.2.9 versus the way it was with OpenOffice hsqldb.jar and 1.8.0.10 . Just not sure how to handle it, that is with WARNINGS, strong WARNINGS to an OpenOffice user, or, problematically, by default, if you know what I mean.

    Sliderule

     
  • Fred:

    I did find a 'pattern' that might help, at least I hope.

    In OpenOffice, if a Table was defined with a Primary Key, and, it is NOT, IDENTITY GENERATED BY DEFAULT, ( for example: "COUNTRY" VARCHAR_IGNORECASE(250) NOT NULL PRIMARY KEY, )OpenOffice will only display the first row.

    On the other hand, if a Table was defined with a Primary Key, INTEGER GENERATED BY DEFAULT AS IDENTITY, in that case, all the records will be displayed for the Table.

    Just a thought on where to start looking for identifying ( database pun intended ) the problem, and, hopefully, the solution.

    Sliderule

     
  • Fred:

    To download a SAMPLE database, OpenOffice 3.3.0 database file using database embedded ( data in OpenOffice ZIP file ) . . . download from:

    http://www.mediafire.com/?q6ksrpaowgk6lsv

    Bottom line, while OpenOffice when using HSQLDB.JAR 2.2.9 Beta Snapshow with a date of 2012-07-28, OpenOffice can open it, BUT, any Table only shows first record.

    Furthermore, and, more important, after closing the OpenOffice Base file, and, re-opening it, the contents of the database is unusable. It return error:

    SQL Status: S1000
    Error code: -25
    error in script file line: 61 java.io.IOException in statement [SET TABLE PUBLIC."WORLD_CONTINENT" INDEX '160 0 8']
    

    It is important to note, the size of the data file ( bytes ) is ALL NULLS.

    Sliderule

     
  • Fred Toussi
    Fred Toussi
    2012-07-29

    Thanks. I have just downloaded the file and will check it later.

     
  • I met same errors when I opened Sliderule file, converted, closed and reopened in OOo which use 2.2.9 snapshot.
    I tested more, created hsqldb server,  copied all files from odb file /database subdirectories to server as test.script, test.data, …etc.

    When I first run server all data was correct. I stopped server with CTRL+C restarted, and I get errors:

    "c:\Users\Zoltan\Documents\OOotest\hsqldb19\hsqldb-2.2.9_snapshot\hsqldb\bin>runS
    erver.bat

    c:\Users\Zoltan\Documents\OOotest\hsqldb19\hsqldb-2.2.9_snapshot\hsqldb\bin>cd .
    .\data
    : [Thread]: checkRunning(false) entered
    : [Thread]: checkRunning(false) exited
    : Startup sequence initiated from main() method
    : Could not load properties from file
    : Using cli/default properties only
    : Initiating startup sequence…
    : Server socket opened successfully in 0 ms.
    2012-07-29T17:41:22.113+0200  WARNING  failed to read a byte array
    java.io.EOFException
            at org.hsqldb.persist.ScaledRAFile.read(ScaledRAFile.java:284)
            at org.hsqldb.persist.ScaledRAFile.readInt(ScaledRAFile.java:275)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:934)
            at org.hsqldb.persist.DataFileCache.getFromFile(DataFileCache.java:860)
            at org.hsqldb.persist.DataFileCache.get(DataFileCache.java:837)
            at org.hsqldb.persist.RowStoreAVLDisk.get(RowStoreAVLDisk.java:112)
            at org.hsqldb.persist.RowStoreAVLDisk.setAccessor(RowStoreAVLDisk.java:3
    19)
            at org.hsqldb.Table.setIndexRoots(Table.java:2530)
            at org.hsqldb.Table.setIndexRoots(Table.java:2574)
            at org.hsqldb.StatementCommand.getResult(StatementCommand.java:864)
            at org.hsqldb.StatementCommand.execute(StatementCommand.java:212)
            at org.hsqldb.Session.executeCompiledStatement(Session.java:1288)
            at org.hsqldb.scriptio.ScriptReaderText.readDDL(ScriptReaderText.java:11
    7)
            at org.hsqldb.scriptio.ScriptReaderBase.readAll(ScriptReaderBase.java:63
    )
            at org.hsqldb.persist.Log.processScript(Log.java:743)
            at org.hsqldb.persist.Log.open(Log.java:147)
            at org.hsqldb.persist.Logger.openPersistence(Logger.java:400)
            at org.hsqldb.Database.reopen(Database.java:231)
            at org.hsqldb.Database.open(Database.java:197)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:255)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:188)
            at org.hsqldb.server.Server.openDatabases(Server.java:1875)
            at org.hsqldb.server.Server.run(Server.java:2208)
            at org.hsqldb.server.Server.access$000(Server.java:243)
            at org.hsqldb.server.Server$ServerThread.run(Server.java:315)

    2012-07-29T17:41:22.113+0200  SEVERE  test.data getFromFile 160
    org.hsqldb.HsqlException: java.io.EOFException
            at org.hsqldb.error.Error.error(Error.java:113)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:941)
            at org.hsqldb.persist.DataFileCache.getFromFile(DataFileCache.java:860)
            at org.hsqldb.persist.DataFileCache.get(DataFileCache.java:837)
            at org.hsqldb.persist.RowStoreAVLDisk.get(RowStoreAVLDisk.java:112)
            at org.hsqldb.persist.RowStoreAVLDisk.setAccessor(RowStoreAVLDisk.java:3
    19)
            at org.hsqldb.Table.setIndexRoots(Table.java:2530)
            at org.hsqldb.Table.setIndexRoots(Table.java:2574)
            at org.hsqldb.StatementCommand.getResult(StatementCommand.java:864)
            at org.hsqldb.StatementCommand.execute(StatementCommand.java:212)
            at org.hsqldb.Session.executeCompiledStatement(Session.java:1288)
            at org.hsqldb.scriptio.ScriptReaderText.readDDL(ScriptReaderText.java:11
    7)
            at org.hsqldb.scriptio.ScriptReaderBase.readAll(ScriptReaderBase.java:63
    )
            at org.hsqldb.persist.Log.processScript(Log.java:743)
            at org.hsqldb.persist.Log.open(Log.java:147)
            at org.hsqldb.persist.Logger.openPersistence(Logger.java:400)
            at org.hsqldb.Database.reopen(Database.java:231)
            at org.hsqldb.Database.open(Database.java:197)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:255)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:188)
            at org.hsqldb.server.Server.openDatabases(Server.java:1875)
            at org.hsqldb.server.Server.run(Server.java:2208)
            at org.hsqldb.server.Server.access$000(Server.java:243)
            at org.hsqldb.server.Server$ServerThread.run(Server.java:315)
    Caused by: java.io.EOFException
            at org.hsqldb.persist.ScaledRAFile.read(ScaledRAFile.java:284)
            at org.hsqldb.persist.ScaledRAFile.readInt(ScaledRAFile.java:275)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:934)
            … 22 more

    2012-07-29T17:41:22.128+0200  WARNING  java.io.EOFException in statement [SET TA
    BLE PUBLIC."WORLD_CONTINENT" INDEX '160 0 8']
    org.hsqldb.HsqlException: java.io.EOFException
            at org.hsqldb.error.Error.error(Error.java:113)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:941)
            at org.hsqldb.persist.DataFileCache.getFromFile(DataFileCache.java:860)
            at org.hsqldb.persist.DataFileCache.get(DataFileCache.java:837)
            at org.hsqldb.persist.RowStoreAVLDisk.get(RowStoreAVLDisk.java:112)
            at org.hsqldb.persist.RowStoreAVLDisk.setAccessor(RowStoreAVLDisk.java:3
    19)
            at org.hsqldb.Table.setIndexRoots(Table.java:2530)
            at org.hsqldb.Table.setIndexRoots(Table.java:2574)
            at org.hsqldb.StatementCommand.getResult(StatementCommand.java:864)
            at org.hsqldb.StatementCommand.execute(StatementCommand.java:212)
            at org.hsqldb.Session.executeCompiledStatement(Session.java:1288)
            at org.hsqldb.scriptio.ScriptReaderText.readDDL(ScriptReaderText.java:11
    7)
            at org.hsqldb.scriptio.ScriptReaderBase.readAll(ScriptReaderBase.java:63
    )
            at org.hsqldb.persist.Log.processScript(Log.java:743)
            at org.hsqldb.persist.Log.open(Log.java:147)
            at org.hsqldb.persist.Logger.openPersistence(Logger.java:400)
            at org.hsqldb.Database.reopen(Database.java:231)
            at org.hsqldb.Database.open(Database.java:197)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:255)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:188)
            at org.hsqldb.server.Server.openDatabases(Server.java:1875)
            at org.hsqldb.server.Server.run(Server.java:2208)
            at org.hsqldb.server.Server.access$000(Server.java:243)
            at org.hsqldb.server.Server$ServerThread.run(Server.java:315)
    Caused by: java.io.EOFException
            at org.hsqldb.persist.ScaledRAFile.read(ScaledRAFile.java:284)
            at org.hsqldb.persist.ScaledRAFile.readInt(ScaledRAFile.java:275)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:934)
            … 22 more

    2012-07-29T17:41:22.128+0200  WARNING  Script processing failure
    org.hsqldb.HsqlException: error in script file line: 61 java.io.EOFException in
    statement
            at org.hsqldb.error.Error.error(Error.java:136)
            at org.hsqldb.scriptio.ScriptReaderText.readDDL(ScriptReaderText.java:14
    8)
            at org.hsqldb.scriptio.ScriptReaderBase.readAll(ScriptReaderBase.java:63
    )
            at org.hsqldb.persist.Log.processScript(Log.java:743)
            at org.hsqldb.persist.Log.open(Log.java:147)
            at org.hsqldb.persist.Logger.openPersistence(Logger.java:400)
            at org.hsqldb.Database.reopen(Database.java:231)
            at org.hsqldb.Database.open(Database.java:197)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:255)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:188)
            at org.hsqldb.server.Server.openDatabases(Server.java:1875)
            at org.hsqldb.server.Server.run(Server.java:2208)
            at org.hsqldb.server.Server.access$000(Server.java:243)
            at org.hsqldb.server.Server$ServerThread.run(Server.java:315)
    Caused by: org.hsqldb.HsqlException: java.io.EOFException
            at org.hsqldb.error.Error.error(Error.java:113)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:941)
            at org.hsqldb.persist.DataFileCache.getFromFile(DataFileCache.java:860)
            at org.hsqldb.persist.DataFileCache.get(DataFileCache.java:837)
            at org.hsqldb.persist.RowStoreAVLDisk.get(RowStoreAVLDisk.java:112)
            at org.hsqldb.persist.RowStoreAVLDisk.setAccessor(RowStoreAVLDisk.java:3
    19)
            at org.hsqldb.Table.setIndexRoots(Table.java:2530)
            at org.hsqldb.Table.setIndexRoots(Table.java:2574)
            at org.hsqldb.StatementCommand.getResult(StatementCommand.java:864)
            at org.hsqldb.StatementCommand.execute(StatementCommand.java:212)
            at org.hsqldb.Session.executeCompiledStatement(Session.java:1288)
            at org.hsqldb.scriptio.ScriptReaderText.readDDL(ScriptReaderText.java:11
    7)
            … 12 more
    Caused by: java.io.EOFException
            at org.hsqldb.persist.ScaledRAFile.read(ScaledRAFile.java:284)
            at org.hsqldb.persist.ScaledRAFile.readInt(ScaledRAFile.java:275)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:934)
            … 22 more

    2012-07-29T17:41:22.269+0200  SEVERE  could not reopen database
    org.hsqldb.HsqlException: error in script file line: 61 java.io.EOFException in
    statement
            at org.hsqldb.error.Error.error(Error.java:136)
            at org.hsqldb.scriptio.ScriptReaderText.readDDL(ScriptReaderText.java:14
    8)
            at org.hsqldb.scriptio.ScriptReaderBase.readAll(ScriptReaderBase.java:63
    )
            at org.hsqldb.persist.Log.processScript(Log.java:743)
            at org.hsqldb.persist.Log.open(Log.java:147)
            at org.hsqldb.persist.Logger.openPersistence(Logger.java:400)
            at org.hsqldb.Database.reopen(Database.java:231)
            at org.hsqldb.Database.open(Database.java:197)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:255)
            at org.hsqldb.DatabaseManager.getDatabase(DatabaseManager.java:188)
            at org.hsqldb.server.Server.openDatabases(Server.java:1875)
            at org.hsqldb.server.Server.run(Server.java:2208)
            at org.hsqldb.server.Server.access$000(Server.java:243)
            at org.hsqldb.server.Server$ServerThread.run(Server.java:315)
    Caused by: org.hsqldb.HsqlException: java.io.EOFException
            at org.hsqldb.error.Error.error(Error.java:113)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:941)
            at org.hsqldb.persist.DataFileCache.getFromFile(DataFileCache.java:860)
            at org.hsqldb.persist.DataFileCache.get(DataFileCache.java:837)
            at org.hsqldb.persist.RowStoreAVLDisk.get(RowStoreAVLDisk.java:112)
            at org.hsqldb.persist.RowStoreAVLDisk.setAccessor(RowStoreAVLDisk.java:3
    19)
            at org.hsqldb.Table.setIndexRoots(Table.java:2530)
            at org.hsqldb.Table.setIndexRoots(Table.java:2574)
            at org.hsqldb.StatementCommand.getResult(StatementCommand.java:864)
            at org.hsqldb.StatementCommand.execute(StatementCommand.java:212)
            at org.hsqldb.Session.executeCompiledStatement(Session.java:1288)
            at org.hsqldb.scriptio.ScriptReaderText.readDDL(ScriptReaderText.java:11
    7)
            … 12 more
    Caused by: java.io.EOFException
            at org.hsqldb.persist.ScaledRAFile.read(ScaledRAFile.java:284)
            at org.hsqldb.persist.ScaledRAFile.readInt(ScaledRAFile.java:275)
            at org.hsqldb.persist.DataFileCache.readObject(DataFileCache.java:934)
            … 22 more

    : [Thread]: Database [index=0, db
    =file:test, alias=] did not open: org.hsqldb.HsqlException: error in script file
    line: 61 java.io.EOFException in statement [SET TABLE PUBLIC."WORLD_CONTINENT"
    INDEX '160 0 8']
    : [Thread]: Shutting down because
    there are no open databases
    : Initiating shutdown sequence…
    : Shutdown sequence completed in 16 ms.
    : 2012-07-29 17:41:22.300 SHUTDOWN : System.exit() is called next."

    If I use SHUTDOWN SCRIPT SQL command, than I can start server again without any problem.

    Same happens when in OOo I use  SHUTDOWN SCRIPT in SQL command window, after reopening the odb file works.

     
  • r4zoli:

    You and I had a conversation in an OpenOffice forum ( Private Messages - http://user.services.openoffice.org/en/forum/ ) about 2012-03-05 and ending 2012-03-13, where it seems hsqldb.jar BETAs, were not working as SERVER with OpenOffice, but, later version of hsqldb.jar did work.

    However, recent hsqldb.jar files, within OpenOffice, will only display one record, I think, when the request uses the Base Parser. Put another way, if within OpenOffice a 'query' is sent directly to the database engine ( hsqldb.jar ) it will return the records. However, if the Base parser generates the request ( and, yes, this includes just opening a Table to 'view it' ), only one record is displayed.

    Just thought I would mention it.

    Sliderule

     
  • Sliderule:
    I missed some background information. I always use with hsqldb 2.2.x the cwshsqldb19 special OOo 3.4 version based on DEV300m106 version with all changes Ocke made and I tested to ready for integration.
    Ocke not joined to AOO and LibO, I suggested to integrate this cws all code to the next version of AOO, I don't know will it happen or not.
    Ocke made some changes in Base UI code to work seamlessly with hsqldb 2.2.x, these changes not in present available versions of AOO or in LibO, you can search AOO bugzilla for "hsqldb19" keyword to find this contain 42 bug 28 solved others not.
    This could be a core problem to you, if you use AOO or LibO any version.

     
  • r4zoli:

    Thank-you for that information. Just so you, and Fred know, I am using OpenOffice 3.3.0 , OOO330m20 ( Build:9567 ) on a Windows XP machine. As of this date, I have never downloaded, nor tried, the AOO version, nor, a LibreOffice version.

    Sliderule

     
  • Fred Toussi
    Fred Toussi
    2012-07-29

    Thank you.

    I am fixing the data loss problem as described by r4Zoli. After that, I will see if a workaround can be introduced in HSQLDB for the "displays just one row" problem. A new snapshot will be available as soon as things are fixed.

    Version 2.2.9 should also work with the CWS. Please test the next snapshot (not the current one) if you can.

     
  • Fred Toussi
    Fred Toussi
    2012-08-04

    I have released a new snapshot jar.

    I fixed the data loss issue and the jar should work fine for external databases and servers.

    As for embedded databases, I tested with internal databases with 3.2 and AOO 3.4. The AOO version (and recent LO) contain many changes introduced last year and do not suffer from the "single row" display issue. However, any data change throws an exception, therefore it is not suitable for normal use.

    I have turned off the ability to open embedded databases with the jar. Developers can uncomment one line from org.hsqldb.persist.HsqlDatabaseProperties which makes it possible.

    Please check with external database use, as well as with the CWS and report any issues.

     
  • I made a short quick test with cws version, no data loss problem during conversion. Works correctly with all existing file which I tested with.

     
  • Fred Toussi
    Fred Toussi
    2012-08-04

    Thank you.

    Further information for developers:

    1. To test with AOO 3.4, uncomment a line in org.hsqldb.persist.HsqlDatabaseProperties#save(). There is a code comment about this.
    2. If a line with SET DATABASE EVENT LOG LEVEL 3 is added to the .script file, or the statement is executed from OO, then an event log file is creates and contains events and any internal exceptions.
    3. OO 3.4 performs a CHECKPOINT on HSQLDB after every statement. This is done from the flush() method of HConnection. This causes an internal error if the user makes any change to data.

     
  • Just a quick note . . . as of 2013-01-04, I would like to report ( see link below ) . . . that HSQL 2.3.0 snapshot jar  . . . works well, without any known issues, with OpenOffice 3.3.0 ( no data loss, whether running a query with or withOUT OpenOffice Base parser ).

    https://sourceforge.net/projects/hsqldb/forums/forum/73674/topic/6561354

    Thanks so much to HSQL team for great efforts.

    Sliderule

     
  • frofa
    frofa
    2013-01-19

    I've been successfully using HSQLDB v.2.2.8 for a while now with 'split' (file mode) databases under LibreOffice (I’m on Mac OS X.6.8 with LO Version 3.6.4.3 and Java™ SE Runtime Environment build 1.6.0_37), but have run into problems apparently similar to those reported to Sliderule above when I tried to upgrade to HSQLDB v.2.2.9. Using v.2.2.9, the first time a click on a TABLE, only ONE line (I think it shows a blank record) is displayed, and this also is the case when I open a FORM linked to a table for the first time. Interestingly, SUBSEQUENT table display queries (re-clicking the table name in the Tables Listing pane) shows the full table listing as expected. This problem does NOT happen with HSQLDB v.2.2.8 which behaves 'normally'. Unlike Sliderule's experience, I have also found that using the latest 'snapshot' v.2.3.0 (dated 4 Jan 2013) does NOT solve this problem.

    One other problem I have is, if I try to revert to using HSQLDB v.2.2.8 (after testing v2.2.9 or 2.3.0 beta), I get an error message ‘error in script file line: 6 unexpected token: REGULAR’ which effectively prevents me from re-opening my DB file in v2.2.8, so I need to use a BACKUP copy of my database (which effectively would mean data loss if I did not if fact have a backup copy). I'd be interested in hear about solutions to both these problems as I would like to keep using the HSQLDB engine with LO and be able to upgrade to take advantage of bug fixes and new features.

     
  • Fred Toussi
    Fred Toussi
    2013-01-19

    It's simple to fix. Open the db.script file and delete line 6 which has SET DATABASE SQL REGULAR NAMES or somthing.

    Actually, you can use the latest 2.3.0 snapshot released today. After saving with this version, there won't be a problem reusing the db with version 2.2.8.

    Please report if today's snapshot has the same issue. We want to fix any remaining problems with 2.3.0

     
  • frofa
    frofa
    2013-01-20

    Thanks for your help fredt. I have tried the latest 'snapshot' version (of 19-1-2013) and it still gives the 'one empty line on first table opening' problem (as described by me above). When I revert to using v.2.2.8 from this latest version I get a different error message saying' error in script file: 33 unexpected token: PAD', but at least I now can fix this particular problem by substituting the previous version of the script file or deleting the line.

     
  • IanS
    IanS
    2013-01-20

    I am using LO 3.6.4.3, Java 1.7.0_09 and Windows 7 and I am having the same problem as reported by frof using hsqldb-20130119.203844-30.jar.

    After opening my database, the first time I open each table, either directly by opening the table or indirectly by opening a query or form based upon the table, the result is a single empty row.  Once each table has been ‘triggered’ in this way all subsequent openings work perfectly and the full dataset is displayed.

    This does not happen with a view. Views open correctly first time. However, opening a view (once or several times) does not ‘trigger’ the associated table so you have the bizzare experience of seeing a complete dataset when using a view but an empty table when, subsequently and for the first time, opening the table upon which the view is based.

    When switching back to 1.8 I get "error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement ".

     
  • Fred Toussi
    Fred Toussi
    2013-01-20

    Thanks. Please note a database created or opened with version 2.x  cannot be switch back to HSQLDB 1.8 . Use version 2.2.8 for the time being, and try with the next 2.3.0 snapshot when it is released

     
  • Fred Toussi
    Fred Toussi
    2013-01-22

    Re auto-increment fields, it seems version 1.8.0 accepted a non-standard statement which has NOT NULL before GENERATED. This is rejected by 2.x.x. I will allow the old non-standard syntax in version 2.3.0

     
  • IanS
    IanS
    2013-01-23

    Re auto-increment fields, it seems version 1.8.0 accepted a non-standard statement which has NOT NULL before GENERATED. This is rejected by 2.x.x. I will allow the old non-standard syntax in version 2.3.0

    The problem with AutoValue fields exists with 1.8.x so I am not sure if what you propose will fix it.

     
  • Fred Toussi
    Fred Toussi
    2013-01-23

    Don't worry about it. It will be fixed for 2.3.0 regardless of 1.8.x

     
  • Fred Toussi
    Fred Toussi
    2013-01-23

    A new snapshot jar for 2.3.0 is available (23 Jan 2013). Tested with AOO 3.4 and LO 3.6.4.3.

    Reported issues have been fixed. Including GENERATED BY DEFAULT, rows not displayed properly.

    You can use this jar for EXTERNAL databases, including jdbc:hsqldb:file: and jdbc:hsqldb:hsql: URL's. It is possible to go back to version 2.2.8 after using this jar to open the database.

    Databases created or opened with this jar cannot be opened with old HSQLDB 1.8.x.

    This jar is still a pre-release jar and is published for tests. We need affirmative reports from several users to be reasonably sure there are no problems. So please test with a copy of your database and report the tasks and results.

    This jar can also be tested with the CWS as it is.

    On a differnet note, for LO, and AOO software developers (not end users), you can compile from SVN with modified (uncommented) line in org.hsqldb.persist.HsqlDatabaseProperties.java and try the jar for INTERNAL embedded .odb databases. This code works much better than the old and allows data modification and shows no error with one database, but it shows errors opening another database. Needs more investigation.

     
1 2 > >> (Page 1 of 2)