You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
(7) |
May
(10) |
Jun
(8) |
Jul
(5) |
Aug
(13) |
Sep
(7) |
Oct
(13) |
Nov
(1) |
Dec
(10) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(5) |
Feb
(3) |
Mar
(23) |
Apr
(23) |
May
(15) |
Jun
(16) |
Jul
(22) |
Aug
(29) |
Sep
(98) |
Oct
(60) |
Nov
(47) |
Dec
(26) |
2003 |
Jan
(30) |
Feb
(36) |
Mar
(54) |
Apr
(96) |
May
(108) |
Jun
(58) |
Jul
(150) |
Aug
(61) |
Sep
(75) |
Oct
(100) |
Nov
(52) |
Dec
(57) |
2004 |
Jan
(93) |
Feb
(82) |
Mar
(183) |
Apr
(73) |
May
(154) |
Jun
(67) |
Jul
(178) |
Aug
(155) |
Sep
(60) |
Oct
(74) |
Nov
(79) |
Dec
(55) |
2005 |
Jan
(81) |
Feb
(103) |
Mar
(74) |
Apr
(102) |
May
(87) |
Jun
(76) |
Jul
(41) |
Aug
(33) |
Sep
(74) |
Oct
(42) |
Nov
(75) |
Dec
(68) |
2006 |
Jan
(36) |
Feb
(21) |
Mar
(67) |
Apr
(71) |
May
(47) |
Jun
(7) |
Jul
(32) |
Aug
(30) |
Sep
(21) |
Oct
(49) |
Nov
(22) |
Dec
(29) |
2007 |
Jan
(48) |
Feb
(17) |
Mar
(23) |
Apr
(31) |
May
(35) |
Jun
(31) |
Jul
(19) |
Aug
(12) |
Sep
(35) |
Oct
(8) |
Nov
(44) |
Dec
(38) |
2008 |
Jan
(74) |
Feb
(77) |
Mar
(17) |
Apr
(21) |
May
(29) |
Jun
(10) |
Jul
(23) |
Aug
(21) |
Sep
(11) |
Oct
(67) |
Nov
(20) |
Dec
(17) |
2009 |
Jan
(17) |
Feb
(30) |
Mar
(56) |
Apr
(61) |
May
(20) |
Jun
(57) |
Jul
(58) |
Aug
(41) |
Sep
(44) |
Oct
(82) |
Nov
(52) |
Dec
(36) |
2010 |
Jan
(33) |
Feb
(43) |
Mar
(37) |
Apr
(57) |
May
(29) |
Jun
(58) |
Jul
(71) |
Aug
(69) |
Sep
(21) |
Oct
(50) |
Nov
(49) |
Dec
(43) |
2011 |
Jan
(64) |
Feb
(36) |
Mar
(54) |
Apr
(50) |
May
(52) |
Jun
(38) |
Jul
(49) |
Aug
(52) |
Sep
(25) |
Oct
(50) |
Nov
(30) |
Dec
(24) |
2012 |
Jan
(22) |
Feb
(56) |
Mar
(28) |
Apr
(40) |
May
(19) |
Jun
(8) |
Jul
(61) |
Aug
(24) |
Sep
(61) |
Oct
(41) |
Nov
(28) |
Dec
(24) |
2013 |
Jan
(17) |
Feb
(24) |
Mar
(22) |
Apr
(7) |
May
(23) |
Jun
(18) |
Jul
(12) |
Aug
(9) |
Sep
(16) |
Oct
(8) |
Nov
(5) |
Dec
(10) |
2014 |
Jan
(10) |
Feb
(3) |
Mar
(13) |
Apr
(1) |
May
(4) |
Jun
(1) |
Jul
(3) |
Aug
(11) |
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
2015 |
Jan
(8) |
Feb
|
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(8) |
Jul
(5) |
Aug
|
Sep
|
Oct
(10) |
Nov
(3) |
Dec
(8) |
2016 |
Jan
|
Feb
(10) |
Mar
(12) |
Apr
(2) |
May
(4) |
Jun
(1) |
Jul
|
Aug
|
Sep
(12) |
Oct
|
Nov
|
Dec
(10) |
2017 |
Jan
(8) |
Feb
(2) |
Mar
(10) |
Apr
(4) |
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
(5) |
Oct
|
Nov
|
Dec
(2) |
2018 |
Jan
(8) |
Feb
|
Mar
(1) |
Apr
(2) |
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(11) |
Jun
(3) |
Jul
|
Aug
(14) |
Sep
(1) |
Oct
(6) |
Nov
(9) |
Dec
(1) |
2020 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
(4) |
Jun
(9) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
(15) |
Dec
(7) |
2021 |
Jan
(4) |
Feb
|
Mar
(2) |
Apr
(13) |
May
|
Jun
|
Jul
(4) |
Aug
(2) |
Sep
|
Oct
(7) |
Nov
(10) |
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(3) |
Jun
(1) |
Jul
(3) |
Aug
(4) |
Sep
|
Oct
(3) |
Nov
(8) |
Dec
|
2023 |
Jan
(4) |
Feb
(1) |
Mar
(13) |
Apr
(1) |
May
(5) |
Jun
(4) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Fred T. <fr...@us...> - 2022-07-04 09:58:04
|
New Release Candidate jars are available here: https://sourceforge.net/projects/hsqldb/files/release_candidate/ Please test and report any issues. Final release is due in a week. Fred Toussi Maintainer, HSQLDB Project |
From: Fred T. <fr...@us...> - 2022-06-01 14:05:27
|
Release candidate jars are available here: https://sourceforge.net/projects/hsqldb/files/release_candidate/ Please test and report any issues. Final release is due in 2 weeks. Fred Toussi Maintainer, HSQLDB Project |
From: Andrew R. <sp...@gm...> - 2022-05-14 12:25:44
|
Hi Fred Thank you for the prompt response. Using the CREATE TABLE variant is a better solution, works like a charm. Thank again, Andrew On Sat, May 14, 2022 at 4:16 AM Fred Toussi via Hsqldb-user < hsq...@li...> wrote: > This won't work because it repeatedly updates by calling the trigger (the > change made in the trigger results in the firing of the same trigger). This > kind of change is done with a BEFORE UPDATE trigger. > > CREATE TRIGGER "WaterResUpdMod" BEFORE UPDATE ON > PUBLIC."WaterfrontReservations" > REFERENCING NEW ROW AS newrow > FOR EACH ROW > SET NEWROW."WaterfrontReservations" = NOW(); > > > See > http://hsqldb.org/doc/2.0/guide/triggers-chapt.html#trc_trigger_action_sql > > Alternatively, you can define the "Modified" table column as automatically > updated in the CREATE TABLE statement. > > "Modified" TIMESTAMP ON UPDATE CURRENT_TIMESTAMP > > See http://hsqldb.org/doc/2.0/guide/databaseobjects-chapt.html > > Fred > > > On Sat, May 14, 2022, at 01:10, Andrew Richardson wrote: > > Hello > Using: HSQLDB 2.6.1 > I am trying to create a trigger such that when a row is changed, > regardless of the client, the table "Modified" field to updated with > current timestamp. I am a newbie in this area. > Below is the table definition and the trigger specification. My test > results in the SQLTool session "hanging" for a short while (~30 seconds) > and then a General error is reported. > Can someone advise what I am doing wrong? Might this be a row lock issue? > Thanks > Andrew Richardson > > sql> \d PUBLIC."WaterfrontReservations" > NAME DATATYPE WIDTH NO-NULLS PRECISION SCALE > ------------ --------- ----- -------- --------- ----- > ID INTEGER 11 * 32 > CustomerID INTEGER 11 * 32 > Notes VARCHAR 128 128 > ResDate DATE 10 10 > NumPeople TINYINT 4 8 > NumKayaks TINYINT 4 8 > NumDblKayaks TINYINT 4 8 > NumCanoes TINYINT 4 8 > NumSUPs TINYINT 4 8 > NumTubes TINYINT 4 8 > NumDblTubes TINYINT 4 8 > NumCoolers TINYINT 4 8 > NumDingys TINYINT 4 8 > PutIn VARCHAR 100 100 > TakeOut VARCHAR 100 100 > LocalInfo VARCHAR 100 100 > LocalPhone VARCHAR 100 100 > TripDate DATE 10 * 10 > TripTime TIME 8 * 8 > NumCChairs TINYINT 4 8 > NumPaddles TINYINT 4 8 > NumPFDs TINYINT 4 8 > NumDays TINYINT 4 8 > BookType VARCHAR 12 12 > Cancelled BOOLEAN 5 > OfficeNotes VARCHAR 128 128 > Modified TIMESTAMP 26 26 6 > > sql> CREATE TRIGGER "WaterResUpdMod" AFTER UPDATE ON > PUBLIC."WaterfrontReservations" > REFERENCING NEW ROW AS newrow > FOR EACH ROW > UPDATE PUBLIC."WaterfrontReservations" SET "Modified" = NOW(); > > ***TEST*** > sql> UPDATE PUBLIC."WaterfrontReservations" SET "CustomerID" = 5289 where > ID = 4234; > SEVERE SQL Error at '<stdin>' line 60: > "UPDATE PUBLIC."WaterfrontReservations" SET "CustomerID" = 5289 where ID = > 4234" > General error > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user > |
From: Fred T. <fr...@us...> - 2022-05-14 08:15:40
|
This won't work because it repeatedly updates by calling the trigger (the change made in the trigger results in the firing of the same trigger). This kind of change is done with a BEFORE UPDATE trigger. > CREATE TRIGGER "WaterResUpdMod" BEFORE UPDATE ON PUBLIC."WaterfrontReservations" > REFERENCING NEW ROW AS newrow > FOR EACH ROW > SET NEWROW."WaterfrontReservations" = NOW(); > See http://hsqldb.org/doc/2.0/guide/triggers-chapt.html#trc_trigger_action_sql Alternatively, you can define the "Modified" table column as automatically updated in the CREATE TABLE statement. "Modified" TIMESTAMP ON UPDATE CURRENT_TIMESTAMP See http://hsqldb.org/doc/2.0/guide/databaseobjects-chapt.html Fred On Sat, May 14, 2022, at 01:10, Andrew Richardson wrote: > Hello > Using: HSQLDB 2.6.1 > I am trying to create a trigger such that when a row is changed, regardless of the client, the table "Modified" field to updated with current timestamp. I am a newbie in this area. > Below is the table definition and the trigger specification. My test results in the SQLTool session "hanging" for a short while (~30 seconds) and then a General error is reported. > Can someone advise what I am doing wrong? Might this be a row lock issue? > Thanks > Andrew Richardson > > sql> \d PUBLIC."WaterfrontReservations" > NAME DATATYPE WIDTH NO-NULLS PRECISION SCALE > ------------ --------- ----- -------- --------- ----- > ID INTEGER 11 * 32 > CustomerID INTEGER 11 * 32 > Notes VARCHAR 128 128 > ResDate DATE 10 10 > NumPeople TINYINT 4 8 > NumKayaks TINYINT 4 8 > NumDblKayaks TINYINT 4 8 > NumCanoes TINYINT 4 8 > NumSUPs TINYINT 4 8 > NumTubes TINYINT 4 8 > NumDblTubes TINYINT 4 8 > NumCoolers TINYINT 4 8 > NumDingys TINYINT 4 8 > PutIn VARCHAR 100 100 > TakeOut VARCHAR 100 100 > LocalInfo VARCHAR 100 100 > LocalPhone VARCHAR 100 100 > TripDate DATE 10 * 10 > TripTime TIME 8 * 8 > NumCChairs TINYINT 4 8 > NumPaddles TINYINT 4 8 > NumPFDs TINYINT 4 8 > NumDays TINYINT 4 8 > BookType VARCHAR 12 12 > Cancelled BOOLEAN 5 > OfficeNotes VARCHAR 128 128 > Modified TIMESTAMP 26 26 6 > > sql> CREATE TRIGGER "WaterResUpdMod" AFTER UPDATE ON PUBLIC."WaterfrontReservations" > REFERENCING NEW ROW AS newrow > FOR EACH ROW > UPDATE PUBLIC."WaterfrontReservations" SET "Modified" = NOW(); > > ***TEST*** > sql> UPDATE PUBLIC."WaterfrontReservations" SET "CustomerID" = 5289 where ID = 4234; > SEVERE SQL Error at '<stdin>' line 60: > "UPDATE PUBLIC."WaterfrontReservations" SET "CustomerID" = 5289 where ID = 4234" > General error > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user > |
From: Andrew R. <sp...@gm...> - 2022-05-14 00:10:40
|
Hello Using: HSQLDB 2.6.1 I am trying to create a trigger such that when a row is changed, regardless of the client, the table "Modified" field to updated with current timestamp. I am a newbie in this area. Below is the table definition and the trigger specification. My test results in the SQLTool session "hanging" for a short while (~30 seconds) and then a General error is reported. Can someone advise what I am doing wrong? Might this be a row lock issue? Thanks Andrew Richardson sql> \d PUBLIC."WaterfrontReservations" NAME DATATYPE WIDTH NO-NULLS PRECISION SCALE ------------ --------- ----- -------- --------- ----- ID INTEGER 11 * 32 CustomerID INTEGER 11 * 32 Notes VARCHAR 128 128 ResDate DATE 10 10 NumPeople TINYINT 4 8 NumKayaks TINYINT 4 8 NumDblKayaks TINYINT 4 8 NumCanoes TINYINT 4 8 NumSUPs TINYINT 4 8 NumTubes TINYINT 4 8 NumDblTubes TINYINT 4 8 NumCoolers TINYINT 4 8 NumDingys TINYINT 4 8 PutIn VARCHAR 100 100 TakeOut VARCHAR 100 100 LocalInfo VARCHAR 100 100 LocalPhone VARCHAR 100 100 TripDate DATE 10 * 10 TripTime TIME 8 * 8 NumCChairs TINYINT 4 8 NumPaddles TINYINT 4 8 NumPFDs TINYINT 4 8 NumDays TINYINT 4 8 BookType VARCHAR 12 12 Cancelled BOOLEAN 5 OfficeNotes VARCHAR 128 128 Modified TIMESTAMP 26 26 6 sql> CREATE TRIGGER "WaterResUpdMod" AFTER UPDATE ON PUBLIC."WaterfrontReservations" REFERENCING NEW ROW AS newrow FOR EACH ROW UPDATE PUBLIC."WaterfrontReservations" SET "Modified" = NOW(); ***TEST*** sql> UPDATE PUBLIC."WaterfrontReservations" SET "CustomerID" = 5289 where ID = 4234; SEVERE SQL Error at '<stdin>' line 60: "UPDATE PUBLIC."WaterfrontReservations" SET "CustomerID" = 5289 where ID = 4234" General error |
From: Fred T. <fr...@us...> - 2022-04-14 08:51:00
|
It is not clear what may be the cause. Enable SQL EVENT LOG LEVEL 2 and see if there is any indication. In the HSLQDB Guide, it is mentioned that NIO use was reported be problematic in some setups. The latest versions of HSQLDB support table spaces. If you turn table spaces on for a database with large cached tables, you probably do not need to do CHECKPOINT DEFRAG so often. Fred On Thu, Apr 14, 2022, at 07:48, Sébastien Pérès-Labourdette wrote: > > Hi. > > Another instance is now causing same issue. > > Everything is fine for a certain amount of time as well as checking instance individually in-process : > - checkpoint / defrag > - perform check all table index and fix > - shutdown > > At some point, unable to checkpoint / defrag properly. > Disk becoming full after a month or so, unable to backup, hsqldb unable to sync io, databases becomes corrupted .... > > What may be causing defrag / checkpoint to hang like that ? > > > > *De : *Fred Toussi Via Hsqldb-user <hsq...@li...> > *Envoyé : * Vendredi 8 Avril 2022 18:18:03 > *À : *Hsqldb User List <hsq...@li...> > *Cc : *Fred Toussi <fr...@us...> > *Objet : *Re: [Hsqldb-user] Blocker on checkpoint >> There's obviusly an issue with the problematic instance. >> >> Execute SHUTDOWN on this particular instance and open it as an in-process database using DatabaseManagerSwing then try "perform check all table index and fix". If it doesn't end, there is something wrong that it cannot fix. Also try SHUTDOWN SCRIPT. If it doesn't work either you can get SupportWare and send the database for a possible fix. >> >> Fred >> >> On Fri, Apr 8, 2022, at 10:39, Sébastien Pérès-Labourdette wrote: >> >>> Hi there. >>> >>> Use case is the following >>> - Hsqldb server 2.5.1 with 14 database instances, some 100% memory, >>> some 100% cached. >>> - Background java job to perform checkpoint defrag on all instances. >>> - Job running well for 4/5 days. >>> - At some point, checkpoint defrag does never end on one specific instance >>> - Shutdown server does never end (waiting for the problematic instance >>> to shutdown but never comes) >>> - Force to kill the server process >>> - Restart server and all goes well for the next 4/5 days >>> >>> The problematic instance does not mention any memory table (all cached) >>> >>> For this one, as well as some others, we have >>> - SET FILES WRITE DELAY FALSE >>> >>> As well as >>> - SET FILES BACKUP INCREMENT TRUE >>> - SET FILES NIO TRUE >>> - SET FILES NIO SIZE 1024 >>> >>> Statements such as "perform check all table index and fix" does never >>> end as well. >>> >>> Storage / hardware is the same for all 14 instances, database "size" is >>> 33Mb, other non-problematic databases goes beyond +600Mb >>> >>> Any clues ? >>> >>> -- >>> Sébastien >>> >>> >>> _______________________________________________ >>> Hsqldb-user mailing list >>> Hsq...@li... >>> https://lists.sourceforge.net/lists/listinfo/hsqldb-user >>> >>> Attachments: >>> * signature.asc >>> >> _______________________________________________ >> Hsqldb-user mailing list >> Hsq...@li... >> https://lists.sourceforge.net/lists/listinfo/hsqldb-user >> > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user > > > *Attachments:* > * signature.asc |
From: Sébastien Pérès-L. <seb...@om...> - 2022-04-14 06:50:12
|
Hi. Another instance is now causing same issue. Everything is fine for a certain amount of time as well as checking instance individually in-process : - checkpoint / defrag - perform check all table index and fix - shutdown At some point, unable to checkpoint / defrag properly. Disk becoming full after a month or so, unable to backup, hsqldb unable to sync io, databases becomes corrupted .... What may be causing defrag / checkpoint to hang like that ? ------------------------------------------------------------------------ *De : *Fred Toussi Via Hsqldb-user <hsq...@li...> *Envoyé : * Vendredi 8 Avril 2022 18:18:03 *À : *Hsqldb User List <hsq...@li...> *Cc : *Fred Toussi <fr...@us...> *Objet : *Re: [Hsqldb-user] Blocker on checkpoint > There's obviusly an issue with the problematic instance. > > Execute SHUTDOWN on this particular instance and open it as an in-process database using DatabaseManagerSwing then try "perform check all table index and fix". If it doesn't end, there is something wrong that it cannot fix. Also try SHUTDOWN SCRIPT. If it doesn't work either you can get SupportWare and send the database for a possible fix. > > Fred > > On Fri, Apr 8, 2022, at 10:39, Sébastien Pérès-Labourdette wrote: >> Hi there. >> >> Use case is the following >> - Hsqldb server 2.5.1 with 14 database instances, some 100% memory, >> some 100% cached. >> - Background java job to perform checkpoint defrag on all instances. >> - Job running well for 4/5 days. >> - At some point, checkpoint defrag does never end on one specific instance >> - Shutdown server does never end (waiting for the problematic instance >> to shutdown but never comes) >> - Force to kill the server process >> - Restart server and all goes well for the next 4/5 days >> >> The problematic instance does not mention any memory table (all cached) >> >> For this one, as well as some others, we have >> - SET FILES WRITE DELAY FALSE >> >> As well as >> - SET FILES BACKUP INCREMENT TRUE >> - SET FILES NIO TRUE >> - SET FILES NIO SIZE 1024 >> >> Statements such as "perform check all table index and fix" does never >> end as well. >> >> Storage / hardware is the same for all 14 instances, database "size" is >> 33Mb, other non-problematic databases goes beyond +600Mb >> >> Any clues ? >> >> -- >> Sébastien >> >> >> _______________________________________________ >> Hsqldb-user mailing list >> Hsq...@li... >> https://lists.sourceforge.net/lists/listinfo/hsqldb-user >> >> Attachments: >> * signature.asc > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user |
From: Fred T. <fr...@us...> - 2022-04-08 16:35:54
|
There's obviusly an issue with the problematic instance. Execute SHUTDOWN on this particular instance and open it as an in-process database using DatabaseManagerSwing then try "perform check all table index and fix". If it doesn't end, there is something wrong that it cannot fix. Also try SHUTDOWN SCRIPT. If it doesn't work either you can get SupportWare and send the database for a possible fix. Fred On Fri, Apr 8, 2022, at 10:39, Sébastien Pérès-Labourdette wrote: > Hi there. > > Use case is the following > - Hsqldb server 2.5.1 with 14 database instances, some 100% memory, > some 100% cached. > - Background java job to perform checkpoint defrag on all instances. > - Job running well for 4/5 days. > - At some point, checkpoint defrag does never end on one specific instance > - Shutdown server does never end (waiting for the problematic instance > to shutdown but never comes) > - Force to kill the server process > - Restart server and all goes well for the next 4/5 days > > The problematic instance does not mention any memory table (all cached) > > For this one, as well as some others, we have > - SET FILES WRITE DELAY FALSE > > As well as > - SET FILES BACKUP INCREMENT TRUE > - SET FILES NIO TRUE > - SET FILES NIO SIZE 1024 > > Statements such as "perform check all table index and fix" does never > end as well. > > Storage / hardware is the same for all 14 instances, database "size" is > 33Mb, other non-problematic databases goes beyond +600Mb > > Any clues ? > > -- > Sébastien > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user > > Attachments: > * signature.asc |
From: Sébastien Pérès-L. <seb...@om...> - 2022-04-08 09:59:14
|
Hi there. Use case is the following - Hsqldb server 2.5.1 with 14 database instances, some 100% memory, some 100% cached. - Background java job to perform checkpoint defrag on all instances. - Job running well for 4/5 days. - At some point, checkpoint defrag does never end on one specific instance - Shutdown server does never end (waiting for the problematic instance to shutdown but never comes) - Force to kill the server process - Restart server and all goes well for the next 4/5 days The problematic instance does not mention any memory table (all cached) For this one, as well as some others, we have - SET FILES WRITE DELAY FALSE As well as - SET FILES BACKUP INCREMENT TRUE - SET FILES NIO TRUE - SET FILES NIO SIZE 1024 Statements such as "perform check all table index and fix" does never end as well. Storage / hardware is the same for all 14 instances, database "size" is 33Mb, other non-problematic databases goes beyond +600Mb Any clues ? -- Sébastien |
From: Fred T. <fr...@us...> - 2021-11-08 14:58:30
|
Thanks. No bug record is required now that it has been fixed. On Mon, Nov 8, 2021, at 14:47, Andrea Spacca wrote: >> I will check with Hibernate later this month. Please open a bug > record with your github link. > > Thanks, in the end it was > exactly:https://hibernate.atlassian.net/browse/HHH-13788 > > Bumping to hibernate 5.5.3 solved the issue. > > > I guess the bug record is not needed, is it? > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user |
From: Andrea S. <and...@gm...> - 2021-11-08 14:47:55
|
> I will check with Hibernate later this month. Please open a bug record with your github link. Thanks, in the end it was exactly:https://hibernate.atlassian.net/browse/HHH-13788 Bumping to hibernate 5.5.3 solved the issue. I guess the bug record is not needed, is it? |
From: Fred T. <fr...@us...> - 2021-11-08 13:51:44
|
I will check with Hibernate later this month. Please open a bug record with your github link. On Mon, Nov 8, 2021, at 08:21, Andrea Spacca wrote: > Still no luck in avoiding re-running all the DDL statements. > > It seems related to https://hibernate.atlassian.net/browse/HHH-13788 > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user |
From: Andrea S. <and...@gm...> - 2021-11-08 08:22:02
|
Still no luck in avoiding re-running all the DDL statements. It seems related to https://hibernate.atlassian.net/browse/HHH-13788 |
From: Fred T. <fr...@us...> - 2021-11-07 13:01:56
|
You should always use the Hibernate HSQLDB dialect. The sql.syntax_pgs=true allows some non-standard features of PostgreSQL in CREATE TABLE and SELECT statements.. You can also remove these 2 settings which may affect the interaction with Hibernate: close_result=true;shutdown=true On Sun, Nov 7, 2021, at 12:29, Andrea Spacca wrote: >> Try without the hbm2ddl setting for Hibernate, and without > sql.lowercase_ident=true for HSQLDB. > > same behaviour. > > I've also deleted the hsqldb files to be sure no previous settings were > affecting the test. > > btw, should I use PostgreSQLDialect if I set "sql.syntax_pgs=true"? > > (not that it did any difference for the specific problem) > > > > Il 07/11/21 12:34, Andrea Spacca ha scritto: >> Thanks for the prompt feedback. >> >> I've already tried different settings for hbm2ddl auto configuration. >> >> If I got it right I should set it to "update": at every restart if there >> any changes in the models they will applied, otherwise not. >> >> Still it tries to reapply every DDL statement as for creation even with >> this value or any other value I set (including "none" or not setting >> anything). >> >> Btw, I tried the same application with H2 embedded in postgres mode and >> no hdm2ddl settings and I didn't face the same issue. >> >> So I'd assume it is a problem on the HSQLDB side, not on hibernate. Do I >> miss anything? >> >> Thanks >> >> >> > Hibernate is covered extensively at StackOverflow. For example: >> >> > >> https://stackoverflow.com/questions/438146/what-are-the-possible-values-of-the-hibernate-hbm2ddl-auto-configuration-and-wha/1689769#1689769 >> >> >> > Regarding your HSQLDB settings, see if you really need >> > sql.lowercase_ident=true. This setting is only necessary if you are >> > using a database access library that assumes (like PostgreSQL) column >> > names in ResultSet are lowercase. >> >> > Fred > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user |
From: Andrea S. <and...@gm...> - 2021-11-07 12:29:51
|
> Try without the hbm2ddl setting for Hibernate, and without sql.lowercase_ident=true for HSQLDB. same behaviour. I've also deleted the hsqldb files to be sure no previous settings were affecting the test. btw, should I use PostgreSQLDialect if I set "sql.syntax_pgs=true"? (not that it did any difference for the specific problem) Il 07/11/21 12:34, Andrea Spacca ha scritto: > Thanks for the prompt feedback. > > I've already tried different settings for hbm2ddl auto configuration. > > If I got it right I should set it to "update": at every restart if there > any changes in the models they will applied, otherwise not. > > Still it tries to reapply every DDL statement as for creation even with > this value or any other value I set (including "none" or not setting > anything). > > Btw, I tried the same application with H2 embedded in postgres mode and > no hdm2ddl settings and I didn't face the same issue. > > So I'd assume it is a problem on the HSQLDB side, not on hibernate. Do I > miss anything? > > Thanks > > > > Hibernate is covered extensively at StackOverflow. For example: > > > > https://stackoverflow.com/questions/438146/what-are-the-possible-values-of-the-hibernate-hbm2ddl-auto-configuration-and-wha/1689769#1689769 > > > > Regarding your HSQLDB settings, see if you really need > > sql.lowercase_ident=true. This setting is only necessary if you are > > using a database access library that assumes (like PostgreSQL) column > > names in ResultSet are lowercase. > > > Fred |
From: Fred T. <fr...@us...> - 2021-11-07 12:19:49
|
Try without the hbm2ddl setting for Hibernate, and without sql.lowercase_ident=true for HSQLDB. On Sun, Nov 7, 2021, at 11:34, Andrea Spacca wrote: > Thanks for the prompt feedback. > > I've already tried different settings for hbm2ddl auto configuration. > > If I got it right I should set it to "update": at every restart if there > any changes in the models they will applied, otherwise not. > > Still it tries to reapply every DDL statement as for creation even with > this value or any other value I set (including "none" or not setting > anything). > > Btw, I tried the same application with H2 embedded in postgres mode and > no hdm2ddl settings and I didn't face the same issue. > > So I'd assume it is a problem on the HSQLDB side, not on hibernate. Do I > miss anything? > > Thanks > > > > Hibernate is covered extensively at StackOverflow. For example: > > > > https://stackoverflow.com/questions/438146/what-are-the-possible-values-of-the-hibernate-hbm2ddl-auto-configuration-and-wha/1689769#1689769 > > > Regarding your HSQLDB settings, see if you really need > > sql.lowercase_ident=true. This setting is only necessary if you are > > using a database access library that assumes (like PostgreSQL) column > > names in ResultSet are lowercase. > > > Fred > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user |
From: Andrea S. <and...@gm...> - 2021-11-07 11:34:59
|
Thanks for the prompt feedback. I've already tried different settings for hbm2ddl auto configuration. If I got it right I should set it to "update": at every restart if there any changes in the models they will applied, otherwise not. Still it tries to reapply every DDL statement as for creation even with this value or any other value I set (including "none" or not setting anything). Btw, I tried the same application with H2 embedded in postgres mode and no hdm2ddl settings and I didn't face the same issue. So I'd assume it is a problem on the HSQLDB side, not on hibernate. Do I miss anything? Thanks > Hibernate is covered extensively at StackOverflow. For example: > https://stackoverflow.com/questions/438146/what-are-the-possible-values-of-the-hibernate-hbm2ddl-auto-configuration-and-wha/1689769#1689769 > Regarding your HSQLDB settings, see if you really need > sql.lowercase_ident=true. This setting is only necessary if you are > using a database access library that assumes (like PostgreSQL) column > names in ResultSet are lowercase. > Fred |
From: Fred T. <fr...@us...> - 2021-11-07 09:34:04
|
Hibernate is covered extensively at StackOverflow. For example: https://stackoverflow.com/questions/438146/what-are-the-possible-values-of-the-hibernate-hbm2ddl-auto-configuration-and-wha/1689769#1689769 Regarding your HSQLDB settings, see if you really need sql.lowercase_ident=true. This setting is only necessary if you are using a database access library that assumes (like PostgreSQL) column names in ResultSet are lowercase. Fred On Sun, Nov 7, 2021, at 09:03, Andrea Spacca wrote: > Hello, > > I'm trying to setup the application at > https://github.com/TeamPiped/Piped-Backend to use an HSQLDB file db. > > I have the following settins: > # Hibernate properties > hibernate.connection.url: > jdbc:hsqldb:file:hsqldb/piped;sql.syntax_pgs=true;sql.lowercase_ident=true;sql.enforce_tdc_delete=false;sql.enforce_tdc_update=false;close_result=true;allow_empty_batch=true;shutdown=true;sql.sys_index_names=false;hsqldb.applog=3;hsqldb.sqllog=3;hsqldb.write_delay=false > hibernate.connection.driver_class: org.hsqldb.jdbcDriver > hibernate.dialect: org.hibernate.dialect.HSQLDialect > hibernate.connection.username: username: > hibernate.connection.password: password: > hibernate.hbm2ddl.auto: create > hibernate.temp.use_jdbc_metadata_defaults: false > hibernate.connection.shutdown: true > > > Everything seems fine but for the fact that at every restart the DDL > statements from hibernate are run again. > > In the SQL logs I can see the following: > 2021-11-07 08:42:46.357 2 select * from information_schema.sequences > 2021-11-07 08:42:46.377 2 SELECT * FROM INFORMATION_SCHEMA.SYSTEM_TABLES > WHERE TRUE AND TABLE_SCHEM IS NULL AND TABLE_NAME LIKE '%' AND > TABLE_TYPE IN ('TABLE','VIEW') > 2021-11-07 08:42:46.399 2 SELECT * FROM > INFORMATION_SCHEMA.SYSTEM_COLUMNS WHERE TRUE AND TABLE_SCHEM IS NULL AND > COLUMN_NAME LIKE '%' > > They are executed at every restart of the application. > My guess is that these statements are run by hibernate in order to > understand what DDL statements to execute in order to setup the db for > the defined Entities. > > Is it my assumption correct? > > Could it be a problem that the table and column names generated from the > entities are not matching the expected ones in the information schema? > (different cases, potential appended prefix, whatever...) > > Did anyone have a similar issue, and how did you solve it? > > Thanks, > Andrea Spacca > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user |
From: Andrea S. <and...@gm...> - 2021-11-07 09:03:35
|
Hello, I'm trying to setup the application at https://github.com/TeamPiped/Piped-Backend to use an HSQLDB file db. I have the following settins: # Hibernate properties hibernate.connection.url: jdbc:hsqldb:file:hsqldb/piped;sql.syntax_pgs=true;sql.lowercase_ident=true;sql.enforce_tdc_delete=false;sql.enforce_tdc_update=false;close_result=true;allow_empty_batch=true;shutdown=true;sql.sys_index_names=false;hsqldb.applog=3;hsqldb.sqllog=3;hsqldb.write_delay=false hibernate.connection.driver_class: org.hsqldb.jdbcDriver hibernate.dialect: org.hibernate.dialect.HSQLDialect hibernate.connection.username: username: hibernate.connection.password: password: hibernate.hbm2ddl.auto: create hibernate.temp.use_jdbc_metadata_defaults: false hibernate.connection.shutdown: true Everything seems fine but for the fact that at every restart the DDL statements from hibernate are run again. In the SQL logs I can see the following: 2021-11-07 08:42:46.357 2 select * from information_schema.sequences 2021-11-07 08:42:46.377 2 SELECT * FROM INFORMATION_SCHEMA.SYSTEM_TABLES WHERE TRUE AND TABLE_SCHEM IS NULL AND TABLE_NAME LIKE '%' AND TABLE_TYPE IN ('TABLE','VIEW') 2021-11-07 08:42:46.399 2 SELECT * FROM INFORMATION_SCHEMA.SYSTEM_COLUMNS WHERE TRUE AND TABLE_SCHEM IS NULL AND COLUMN_NAME LIKE '%' They are executed at every restart of the application. My guess is that these statements are run by hibernate in order to understand what DDL statements to execute in order to setup the db for the defined Entities. Is it my assumption correct? Could it be a problem that the table and column names generated from the entities are not matching the expected ones in the information schema? (different cases, potential appended prefix, whatever...) Did anyone have a similar issue, and how did you solve it? Thanks, Andrea Spacca |
From: Fred T. <fr...@us...> - 2021-10-21 15:03:59
|
Version 2.6.1 download package is now available at SourceForge via http://hsqldb.org <http://hsqldb.org/download/> The default jars require Java 11 or later and can be used as Java modules. Java 8 versions of the jars are also included in the package. Jars for Java 6 are available from http://hsqldb.org/download/ The documentation on the web site covers the latest release.Jars will be released to Maven in the next few days. Fred Toussi HSQL Development Group |
From: Fred T. <fr...@us...> - 2021-10-14 21:43:46
|
See ha-jdbc on github. There may be others as well. On Thu, Oct 14, 2021, at 09:21, Sébastien Pérès-Labourdette wrote: > Hi there. > > Does somebody has ever implemented an hsqldb server load balancing cluster ? > > -- > Sébastien > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user > > Attachments: > * signature.asc |
From: Sébastien Pérès-L. <seb...@om...> - 2021-10-14 08:36:47
|
Hi there. Does somebody has ever implemented an hsqldb server load balancing cluster ? -- Sébastien |
From: Jorge G. de A. <jor...@gm...> - 2021-10-13 23:27:37
|
Hello, I decided to log everything into a table instead. //Create source table CREATE TABLE atable ( id LONGVARCHAR, name LONGVARCHAR ); //Insert source table values INSERT INTO atable (id,name) VALUES ('0','a'); INSERT INTO atable (id,name) VALUES ('1','b'); INSERT INTO atable (id,name) VALUES ('2','c'); //Create table for output CREATE TABLE output ( String LONGVARCHAR ); //Create print procedure CREATE PROCEDURE print ( IN v_String LONGVARCHAR ) MODIFIES SQL DATA BEGIN ATOMIC INSERT INTO output ( String ) VALUES ( v_String ); END; //Create test procedure CREATE PROCEDURE theprocedure() -- modifies sql data BEGIN atomic -- FOR SELECT id,name FROM atable DO -- call print(id+','+name); -- END FOR; -- END; //Run test procedure CALL theprocedure(); |
From: Jorge G. de A. <jor...@gm...> - 2021-10-13 22:37:38
|
Excellent. I will try that. Thanks. On 10/13/21, Fred Toussi via Hsqldb-user <hsq...@li...> wrote: > You can create a Java static method to log a message and CREATE a SQL/JRT > FUNCTION for this method. Then call this FUNCTION from your procedure or > function with the message you want to log. > > On Wed, Oct 13, 2021, at 16:24, Jorge Garcia de Alba wrote: >> Hello, >> >> When working with procedures, is there a way to print the variables >> out to console or log? Thanks. Have a great day. >> >> Jorge >> >> >> _______________________________________________ >> Hsqldb-user mailing list >> Hsq...@li... >> https://lists.sourceforge.net/lists/listinfo/hsqldb-user > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user > |
From: Fred T. <fr...@us...> - 2021-10-13 22:16:02
|
You can create a Java static method to log a message and CREATE a SQL/JRT FUNCTION for this method. Then call this FUNCTION from your procedure or function with the message you want to log. On Wed, Oct 13, 2021, at 16:24, Jorge Garcia de Alba wrote: > Hello, > > When working with procedures, is there a way to print the variables > out to console or log? Thanks. Have a great day. > > Jorge > > > _______________________________________________ > Hsqldb-user mailing list > Hsq...@li... > https://lists.sourceforge.net/lists/listinfo/hsqldb-user |