bruno KONIK

I have forgotten that the HISTORY table is created like this : "CREATE CACHED TABLE history (id BIGINT IDENTITY, userid VARCHAR(50).....".

Hello, HSQLDB 2.71. We have had an error when starting a HSQLDB Server (launched from a Linux service) after having stopped it (stopping the Linux service). The table is named HISTORY with 4 indexes. The error is this one : java.sql.SQLIntegrityConstraintViolationException: integrity constraint violation: unique constraint or index violation ; SYS_PK_10093 table: HISTORY If I launched the command "PERFORM CHECK TABLE PUBLIC.HISTORY INDEX;" I get this. 6 elements TABLE_NAME;INDEX_NAME;INFO; PUBLIC.HISTORY;;rows...

I understand this behavior but in my opinion it is a bit dangerous. The user may well be interrupted while he is editing the entry and may forget to save or cancel it. I would suggest another possibility when the inactivity occurs while editing an entry. You could open a dialog box asking the user to save the database and before saving (or not depending on his choice) ask the password. Of course you take the risk that another user saves the database with unwanted data but is it more dangerous than...

I have the same behavior. I would consider it as a bug because this prevents the workspace lock.

Hi Fred, Yes, the snapshot seems to have fixed the problem. Thank you much. It will be present in the next release I presume. Bruno De : Fred Toussi [mailto:fredt@users.sourceforge.net] Envoyé : lundi 10 juin 2019 14:41 À : [hsqldb:bugs] 1547@bugs.hsqldb.p.re.sourceforge.net Objet : [hsqldb:bugs] #1547 When trying to access a running HSQLDB process, a NPE ocurs There was a regression in version 2.5.0 which is now fixed. Please download and test the SVN trunk HEAD as I suggested. [bugs:#1547] https://sourceforge.net/p/hsqldb/bugs/1547/...

Hello Fred, Thanks for your fast answer. How do you explain that it has never failed with the 2.3.3 version ? You can see below that there is no NPE and that the process which tries to connect to the database has got no problem doing so. Here is the log when using 2.3.3 in the same situation : 2019-06-10 11:03:18,774 [TelServerDbProcess] INFO TelServerDb - Starting TelServer embedded database... 2019-06-10 11:03:18,925 [TelServerDbProcess] TRACE TelServerDb - [Server@2aae9190]: [Thread[main,5,main]]:...

Hi Fred, To provide more information. Our server launches a ProcessBuilder for hsqldb and supervises the Server.getState() to detect if the server has stopped (we test Server.getState() == 16 - that is ServerProperties.SERVER_STATE_SHUTDOWN) . If there is a NPE, it seems that our test cannot function as we expect since the state is never set to 16. Do you have a hint to ensure that the server is stopped even if there is this NPE ? I think that avoiding the NPE would make the state set to 16 but I...

When trying to access a running HSQLDB process, a NPE ocurs