hsqldb-developers — A list to discuss issues of interest to developers of the hsqldb Database Engine

Re: [Hsqldb-developers] Upgraded to 2.5.1 - getting org.hsqldb.HsqlException: lob is no longer valid

[Fred T. <fr...@us...>]

Yes, with a mem: database, this change could be the reason. Add hsqldb.log_size=0 to your connection URL to avoid automatic checkpoint which clear the deleted lobs.

Fred

On Thu, Sep 3, 2020, at 19:08, Bryan Coleman wrote:
> Upgraded from version 2.5.0 to 2.5.1.
> 
> Periodically, I receive the following HsqlException (org.hsqldb.HsqlException: lob is no longer valid)
> 
> Stack Trace:
>   at org.hsqldb.error.Error.error(Unknown Source)
>   at org.hsqldb.error.Error.error(Unknown Source)
>   at org.hsqldb.persist.LobManager.getLength(Unknown Source)
>   at org.hsqldb.Session.performLOBOperation(Unknown Source)
>   at org.hsqldb.Session.execute(Unknown Source)
>   at org.hsqldb.types.BlobDataID.length(Unknown Source)
>   at org.hsqldb.jdbc.JDBCResultSet.getBytes(Unknown Source)
>   at org.hsqldb.jdbc.JDBCResultSet.getBytes(Unknown Source)
>   at org.apache.commons.dbcp2.DelegatingResultSet.getBytes(DelegatingResultSet.java:408)
> 
> caused by a call to ResultSet.getBytes(String column)
> 
> Curious, if it has something to do with the update noted in the changelog *"added support for reuse of memory space for lobs in mem: databases".*
> 
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
> 

[Hsqldb-developers] Upgraded to 2.5.1 - getting org.hsqldb.HsqlException: lob is no longer valid

[Bryan C. <bla...@gm...>]

Upgraded from version 2.5.0 to 2.5.1.

Periodically, I receive the following HsqlException
(org.hsqldb.HsqlException: lob is no longer valid)

Stack Trace:
  at org.hsqldb.error.Error.error(Unknown Source)
  at org.hsqldb.error.Error.error(Unknown Source)
  at org.hsqldb.persist.LobManager.getLength(Unknown Source)
  at org.hsqldb.Session.performLOBOperation(Unknown Source)
  at org.hsqldb.Session.execute(Unknown Source)
  at org.hsqldb.types.BlobDataID.length(Unknown Source)
  at org.hsqldb.jdbc.JDBCResultSet.getBytes(Unknown Source)
  at org.hsqldb.jdbc.JDBCResultSet.getBytes(Unknown Source)
  at
org.apache.commons.dbcp2.DelegatingResultSet.getBytes(DelegatingResultSet.java:408)

caused by a call to ResultSet.getBytes(String column)

Curious, if it has something to do with the update noted in the
changelog *"added
support for reuse of memory space for lobs in mem: databases". *

Re: [Hsqldb-developers] Session.TimeoutManager oversimpliefied (bugged) in hsql 2.5.0?

[Fred T. <fr...@us...>]

Thanks for reporting Thorsten,

I will check and commit changes to SVN so you can test. The next release is due next month as there were a few regressions in 2.5.0 that have been fixed since the release.

Regards

Fred Toussi

On Tue, Aug 20, 2019, at 14:49, Thorsten Goetzke wrote:
> Hello,
> 
> We updated from hsql 2.4.1 to 2.5.0. Now we are seeing getting timeout 
> exceptions, which appear to be incorrect, because the queries weren't 
> nearly running as long as the specified query time.
> Sorry, I cannot produce a small self contained example at this time.
> After skimming throught the source code it seems to me that current 
> TimeoutSessionManager implementation is faulty.
> 
> Lets assume a query gets started using a timeout of 15 seconds (15.000 
> millis)
> 
> This will call TimeoutManager#startTimeout(15.000)
> 
> later #checkTimeout will be called from a different thread.
> The first statement
> currentTimeout.get() == 0
> will evaluate to false, so the method will continue
> Lets asume now the scheduler will switch back to the running query, 
> executes it finishes it and executes the next one, using no timeout (0)...
> So now
> currentTimeout== 0
> Now let the scheduler swich back to #checkTimeout
> now the statement currentTimeout.decrementAndGet() will evaluate and of 
> course it will return -1 -> The session gets reseted even though it did 
> nothing wrong ;)
> The TimeoutManagerCode from hsql 2.4.1 did validate a timestamp which 
> seems like an appropriate aproach to me.
> 
> Also did i evaluate something wrong or are all timeouts multiplied by 
> 1000 ? (current timeout will get at most be decremented by one every 
> second ?)
> 
> Offending Exception below and
> 
> Best regards,
> Thorsten Goetzke
> 
> 
> 
> 
> er] Caused by: java.sql.SQLTransactionRollbackException: statement 
> execution aborted: timeout reached
> [09:53:04] :													 [junitlauncher] 	at 
> org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
> [09:53:04] :													 [junitlauncher] 	at 
> org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
> [09:53:04] :													 [junitlauncher] 	at 
> org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(Unknown Source)
> [09:53:04] :													 [junitlauncher] 	at 
> org.hsqldb.jdbc.JDBCPreparedStatement.executeQuery(Unknown Source)
> [09:53:04] :													 [junitlauncher] 	at 
> org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:70)
> [09:53:04] :													 [junitlauncher] 	... 21 more
> [09:53:04] :													 [junitlauncher] Caused by: 
> org.hsqldb.HsqlException: statement execution aborted: timeout reached
> [09:53:04] :													 [junitlauncher] 	at 
> org.hsqldb.error.Error.error(Unknown Source)
> [09:53:04] :													 [junitlauncher] 	at 
> org.hsqldb.error.Error.error(Unknown Source)
> [09:53:04] :													 [junitlauncher] 	at 
> org.hsqldb.Session.executeCompiledStatement(Unknown Source)
> [09:53:04] :													 [junitlauncher] 	at 
> org.hsqldb.Session.execute(Unknown Source)
> 
> 
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>

[Hsqldb-developers] Session.TimeoutManager oversimpliefied (bugged) in hsql 2.5.0?

[Thorsten G. <tg...@fr...>]

Hello,

We updated from hsql 2.4.1 to 2.5.0. Now we are seeing getting timeout 
exceptions, which appear to be incorrect, because the queries weren't 
nearly running as long as the specified query time.
Sorry, I cannot produce a small self contained example at this time.
After skimming throught the source code it seems to me that current 
TimeoutSessionManager implementation is faulty.

Lets assume a query gets started using a timeout of 15 seconds (15.000 
millis)

This will call TimeoutManager#startTimeout(15.000)

later #checkTimeout will be called from a different thread.
The first statement
currentTimeout.get() == 0
will evaluate to false, so the method will continue
Lets asume now the scheduler will switch back to the running query, 
executes it finishes it and executes the next one, using no timeout (0)...
So now
currentTimeout== 0
Now let the scheduler swich back to #checkTimeout
now the statement currentTimeout.decrementAndGet() will evaluate and of 
course it will return -1 -> The session gets reseted even though it did 
nothing wrong ;)
The TimeoutManagerCode from hsql 2.4.1 did validate a timestamp which 
seems like an appropriate aproach to me.

Also did i evaluate something wrong or are all timeouts multiplied by 
1000 ? (current timeout will get at most be decremented by one every 
second ?)

Offending Exception below and

Best regards,
Thorsten Goetzke




er] Caused by: java.sql.SQLTransactionRollbackException: statement 
execution aborted: timeout reached
[09:53:04] :													 [junitlauncher] 	at 
org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
[09:53:04] :													 [junitlauncher] 	at 
org.hsqldb.jdbc.JDBCUtil.sqlException(Unknown Source)
[09:53:04] :													 [junitlauncher] 	at 
org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(Unknown Source)
[09:53:04] :													 [junitlauncher] 	at 
org.hsqldb.jdbc.JDBCPreparedStatement.executeQuery(Unknown Source)
[09:53:04] :													 [junitlauncher] 	at 
org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:70)
[09:53:04] :													 [junitlauncher] 	... 21 more
[09:53:04] :													 [junitlauncher] Caused by: 
org.hsqldb.HsqlException: statement execution aborted: timeout reached
[09:53:04] :													 [junitlauncher] 	at 
org.hsqldb.error.Error.error(Unknown Source)
[09:53:04] :													 [junitlauncher] 	at 
org.hsqldb.error.Error.error(Unknown Source)
[09:53:04] :													 [junitlauncher] 	at 
org.hsqldb.Session.executeCompiledStatement(Unknown Source)
[09:53:04] :													 [junitlauncher] 	at 
org.hsqldb.Session.execute(Unknown Source)

[Hsqldb-developers] how to reduce .lob file size in hsqldb

[soham <so...@el...>]

Hello , 

i am using hsqldb-2.3.4 version. In my DB .lob file size is growing and
today it is 55GB. 
by deleting lob data file size is not reduced. 
please let me know how to reduce .lob file size.

Thanks,

Soham



--
Sent from: http://hsqldb.10974.n7.nabble.com/HSQLDB-Dev-f3585.html

Re: [Hsqldb-developers] HTTP 404 when attempting to fetch trunk

[Mahesh C. D. <mah...@vm...>]

Hi Andrey,

Sorry! I am not aware of this SVN repository.



*Thanks & Regards,*



*Mahesh Devda*
*Software Engineer*

*Vmoksha Technologies** /*  *www.vmokshagroup.com*
<http://www.vmokshagroup.com/>

*ISO 27001:2013 Certified Company*

#2799 & 2800, Srinidhi, Sector-1, 27th Main, HSR Layout,

Bangalore – 560102, Karnataka, India.

 *+91 80* *4137 6300 100*

*[image: https://www.facebook.com/Vmokshagroup]
<https://www.facebook.com/Vmokshagroup> [image:
http://www.linkedin.com/company/vmoksha-technologies]
<http://www.linkedin.com/company/vmoksha-technologies>
<https://twitter.com/infovmoksha>*

On Mon, Mar 5, 2018 at 5:09 PM, Andrey Shcheglov <
and...@je...> wrote:

> Hello,
>
> For some reason, an attempt to access the Subversion trunk
> (https://svn.code.sf.net/p/hsqldb/svn/base/trunk/) results in an HTTP 404.
>
> Is the repository consistent?
>
> Regards,
> Andrey.
>
> --
> Best regards,
>
> Andrey Shcheglov
> Software Engineer
>
> JetBrains
> http://www.jetbrains.com
> The Drive to Develop
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>

-- 

------------------------------

Disclaimer: The information contained in this message is legally privileged 
and confidential information intended only for the use of the addressed 
individual or entity indicated in this message (or responsible for delivery 
of the message to such person). It must not be read, copied, disclosed, 
distributed or used by any person other than the addressee.
Unauthorized use, disclosure or copying is strictly prohibited and may be 
unlawful. Opinions, conclusions and other information on this message that 
do not relate to the official business of any of the constituent companies 
of VMOKSHA shall be understood as neither given nor endorsed by the Group. 
If you have received this message in error, you should destroy this message 
and kindly notify the sender by e-mail. No responsibility is accepted for 
any virus or defect that might arise from opening this e-mail or 
attachments, whether or not it has been checked by anti-virus 
software.Individual employee/s shall be accountable / responsible for 
sending illegitimate emails.

Re: [Hsqldb-developers] HTTP 404 when attempting to fetch trunk

[Andrey S. <and...@je...>]

Thank you Fred.

Regards,
Andrey.

On 05.03.2018 15:09, Fred Toussi via hsqldb-developers wrote:
> SourceForge has had a lot of intermittent problems after migration to new servers. I was not able to commit for a while until yesterday. An hour ago there was a support ticket on SourceForge "#17078 Subversion service randomly fails".  There have been some tweets on twitter #sourceforge while the whole site was down. 

Re: [Hsqldb-developers] HTTP 404 when attempting to fetch trunk

[Fred T. <fr...@us...>]

SourceForge has had a lot of intermittent problems after migration to new servers. I was not able to commit for a while until yesterday. An hour ago there was a support ticket on SourceForge "#17078 Subversion service randomly fails".  There have been some tweets on twitter #sourceforge while the whole site was down. 

Fred 

On Mon, Mar 5, 2018, at 11:39, Andrey Shcheglov wrote:
> Hello,
> 
> For some reason, an attempt to access the Subversion trunk
> (https://svn.code.sf.net/p/hsqldb/svn/base/trunk/) results in an HTTP 404.
> 
> Is the repository consistent?
> 
> Regards,
> Andrey.
> 
> -- 
> Best regards,
> 
> Andrey Shcheglov
> Software Engineer
> 
> JetBrains
> http://www.jetbrains.com
> The Drive to Develop
> 
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

[Hsqldb-developers] HTTP 404 when attempting to fetch trunk

[Andrey S. <and...@je...>]

Hello,

For some reason, an attempt to access the Subversion trunk
(https://svn.code.sf.net/p/hsqldb/svn/base/trunk/) results in an HTTP 404.

Is the repository consistent?

Regards,
Andrey.

-- 
Best regards,

Andrey Shcheglov
Software Engineer

JetBrains
http://www.jetbrains.com
The Drive to Develop

Re: [Hsqldb-developers] Problem connecting to HSQLDB with 2.4.0 vesion

[Fred T. <fr...@us...>]

The problem is caused by an old copy of the HSQLDB jar (older than version 2.0) in your web application classpath. Check the jars and replace them all with version 2.4.0

Please check http://hsqldb.org/support if you have any future help requests and post in the appropriate help forum.

Fred

On Thu, Mar 1, 2018, at 06:52, maheshde via hsqldb-developers wrote:
> I am facing problem while connecting to the HSQLDB. I am using HSQLDB 2.4.0.
> Also, I have tried to  HSQLDB 2.3.0, 2.3.4 JAR but no luck. 
> 
> I have one standalone program in this program I am creating a database and
> all table by running script files.
> 
> I have another web application in that application I am using this database
> to insert/update/delete operations. The problem is after creating the
> database/table when I am connecting to the database from web application I
> am getting below exception:
> 
> *Failed to get hsqldb connection: java.sql.SQLException: error in script
> file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET
> DATABASE UNIQUE]  *
> 
> Here is my .script file.
> 
> SET DATABASE UNIQUE NAME HSQLDB61DCB90D14
> SET DATABASE GC 0
> SET DATABASE DEFAULT RESULT MEMORY ROWS 0
> SET DATABASE EVENT LOG LEVEL 0
> SET DATABASE SQL NAMES FALSE
> SET DATABASE SQL REFERENCES FALSE
> SET DATABASE SQL SIZE TRUE
> SET DATABASE SQL TYPES FALSE
> SET DATABASE SQL TDC DELETE TRUE
> SET DATABASE SQL TDC UPDATE TRUE
> SET DATABASE SQL TRANSLATE TTI TYPES TRUE
> SET DATABASE SQL CONCAT NULLS TRUE
> SET DATABASE SQL UNIQUE NULLS TRUE
> SET DATABASE SQL CONVERT TRUNCATE TRUE
> SET DATABASE SQL AVG SCALE 0
> SET DATABASE SQL DOUBLE NAN TRUE
> SET DATABASE TRANSACTION CONTROL LOCKS
> SET DATABASE DEFAULT ISOLATION LEVEL READ COMMITTED
> SET DATABASE TRANSACTION ROLLBACK ON CONFLICT TRUE
> SET DATABASE TEXT TABLE DEFAULTS ''
> SET FILES WRITE DELAY 500 MILLIS
> SET FILES BACKUP INCREMENT TRUE
> SET FILES CACHE SIZE 10000
> SET FILES CACHE ROWS 50000
> SET FILES SCALE 32
> SET FILES LOB SCALE 32
> SET FILES DEFRAG 0
> SET FILES NIO TRUE
> SET FILES NIO SIZE 256
> SET FILES LOG TRUE
> SET FILES LOG SIZE 50
> CREATE USER SA PASSWORD DIGEST 'd41d8cd98f00b204e9800998ecf8427e'
> ALTER USER SA SET LOCAL TRUE
> CREATE SCHEMA PUBLIC AUTHORIZATION DBA
> ALTER SEQUENCE SYSTEM_LOBS.LOB_ID RESTART WITH 1
> SET DATABASE DEFAULT INITIAL SCHEMA PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.YES_OR_NO TO PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.TIME_STAMP TO PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.CARDINAL_NUMBER TO PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.CHARACTER_DATA TO PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.SQL_IDENTIFIER TO PUBLIC
> GRANT DBA TO SA
> 
> *.property file*
> 
> #HSQL Database Engine 2.3.0 
> #Wed Feb 28 19:32:50 IST 2018 
> version=2.3.0 
> modified=yes 
> 
> 
> 
> --
> Sent from: http://hsqldb.10974.n7.nabble.com/HSQLDB-Dev-f3585.html
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

Re: [Hsqldb-developers] Problem connecting to HSQLDB with 2.4.0 vesion

[Fred T. <ft...@cl...>]

The problem is caused by an old copy of the HSQLDB jar (older than version 2.0) in your web application classpath. Check the jars and replace them all with version 2.4.0

Please check http://hsqldb.org/support if you have any future help requests and post in the appropriate help forum.

Fred

On Thu, Mar 1, 2018, at 06:52, maheshde via hsqldb-developers wrote:
> I am facing problem while connecting to the HSQLDB. I am using HSQLDB 2.4.0.
> Also, I have tried to  HSQLDB 2.3.0, 2.3.4 JAR but no luck. 
> 
> I have one standalone program in this program I am creating a database and
> all table by running script files.
> 
> I have another web application in that application I am using this database
> to insert/update/delete operations. The problem is after creating the
> database/table when I am connecting to the database from web application I
> am getting below exception:
> 
> *Failed to get hsqldb connection: java.sql.SQLException: error in script
> file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET
> DATABASE UNIQUE]  *
> 
> Here is my .script file.
> 
> SET DATABASE UNIQUE NAME HSQLDB61DCB90D14
> SET DATABASE GC 0
> SET DATABASE DEFAULT RESULT MEMORY ROWS 0
> SET DATABASE EVENT LOG LEVEL 0
> SET DATABASE SQL NAMES FALSE
> SET DATABASE SQL REFERENCES FALSE
> SET DATABASE SQL SIZE TRUE
> SET DATABASE SQL TYPES FALSE
> SET DATABASE SQL TDC DELETE TRUE
> SET DATABASE SQL TDC UPDATE TRUE
> SET DATABASE SQL TRANSLATE TTI TYPES TRUE
> SET DATABASE SQL CONCAT NULLS TRUE
> SET DATABASE SQL UNIQUE NULLS TRUE
> SET DATABASE SQL CONVERT TRUNCATE TRUE
> SET DATABASE SQL AVG SCALE 0
> SET DATABASE SQL DOUBLE NAN TRUE
> SET DATABASE TRANSACTION CONTROL LOCKS
> SET DATABASE DEFAULT ISOLATION LEVEL READ COMMITTED
> SET DATABASE TRANSACTION ROLLBACK ON CONFLICT TRUE
> SET DATABASE TEXT TABLE DEFAULTS ''
> SET FILES WRITE DELAY 500 MILLIS
> SET FILES BACKUP INCREMENT TRUE
> SET FILES CACHE SIZE 10000
> SET FILES CACHE ROWS 50000
> SET FILES SCALE 32
> SET FILES LOB SCALE 32
> SET FILES DEFRAG 0
> SET FILES NIO TRUE
> SET FILES NIO SIZE 256
> SET FILES LOG TRUE
> SET FILES LOG SIZE 50
> CREATE USER SA PASSWORD DIGEST 'd41d8cd98f00b204e9800998ecf8427e'
> ALTER USER SA SET LOCAL TRUE
> CREATE SCHEMA PUBLIC AUTHORIZATION DBA
> ALTER SEQUENCE SYSTEM_LOBS.LOB_ID RESTART WITH 1
> SET DATABASE DEFAULT INITIAL SCHEMA PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.YES_OR_NO TO PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.TIME_STAMP TO PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.CARDINAL_NUMBER TO PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.CHARACTER_DATA TO PUBLIC
> GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.SQL_IDENTIFIER TO PUBLIC
> GRANT DBA TO SA
> 
> *.property file*
> 
> #HSQL Database Engine 2.3.0 
> #Wed Feb 28 19:32:50 IST 2018 
> version=2.3.0 
> modified=yes 
> 
> 
> 
> --
> Sent from: http://hsqldb.10974.n7.nabble.com/HSQLDB-Dev-f3585.html
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

[Hsqldb-developers] Problem connecting to HSQLDB with 2.4.0 vesion

[maheshde <mah...@vm...>]

I am facing problem while connecting to the HSQLDB. I am using HSQLDB 2.4.0.
Also, I have tried to  HSQLDB 2.3.0, 2.3.4 JAR but no luck. 

I have one standalone program in this program I am creating a database and
all table by running script files.

I have another web application in that application I am using this database
to insert/update/delete operations. The problem is after creating the
database/table when I am connecting to the database from web application I
am getting below exception:

*Failed to get hsqldb connection: java.sql.SQLException: error in script
file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET
DATABASE UNIQUE]  *

Here is my .script file.

SET DATABASE UNIQUE NAME HSQLDB61DCB90D14
SET DATABASE GC 0
SET DATABASE DEFAULT RESULT MEMORY ROWS 0
SET DATABASE EVENT LOG LEVEL 0
SET DATABASE SQL NAMES FALSE
SET DATABASE SQL REFERENCES FALSE
SET DATABASE SQL SIZE TRUE
SET DATABASE SQL TYPES FALSE
SET DATABASE SQL TDC DELETE TRUE
SET DATABASE SQL TDC UPDATE TRUE
SET DATABASE SQL TRANSLATE TTI TYPES TRUE
SET DATABASE SQL CONCAT NULLS TRUE
SET DATABASE SQL UNIQUE NULLS TRUE
SET DATABASE SQL CONVERT TRUNCATE TRUE
SET DATABASE SQL AVG SCALE 0
SET DATABASE SQL DOUBLE NAN TRUE
SET DATABASE TRANSACTION CONTROL LOCKS
SET DATABASE DEFAULT ISOLATION LEVEL READ COMMITTED
SET DATABASE TRANSACTION ROLLBACK ON CONFLICT TRUE
SET DATABASE TEXT TABLE DEFAULTS ''
SET FILES WRITE DELAY 500 MILLIS
SET FILES BACKUP INCREMENT TRUE
SET FILES CACHE SIZE 10000
SET FILES CACHE ROWS 50000
SET FILES SCALE 32
SET FILES LOB SCALE 32
SET FILES DEFRAG 0
SET FILES NIO TRUE
SET FILES NIO SIZE 256
SET FILES LOG TRUE
SET FILES LOG SIZE 50
CREATE USER SA PASSWORD DIGEST 'd41d8cd98f00b204e9800998ecf8427e'
ALTER USER SA SET LOCAL TRUE
CREATE SCHEMA PUBLIC AUTHORIZATION DBA
ALTER SEQUENCE SYSTEM_LOBS.LOB_ID RESTART WITH 1
SET DATABASE DEFAULT INITIAL SCHEMA PUBLIC
GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.YES_OR_NO TO PUBLIC
GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.TIME_STAMP TO PUBLIC
GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.CARDINAL_NUMBER TO PUBLIC
GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.CHARACTER_DATA TO PUBLIC
GRANT USAGE ON DOMAIN INFORMATION_SCHEMA.SQL_IDENTIFIER TO PUBLIC
GRANT DBA TO SA

*.property file*

#HSQL Database Engine 2.3.0 
#Wed Feb 28 19:32:50 IST 2018 
version=2.3.0 
modified=yes 



--
Sent from: http://hsqldb.10974.n7.nabble.com/HSQLDB-Dev-f3585.html

Re: [Hsqldb-developers] OUT VALUE on Stored Procedures

[Albert M. <alb...@gm...>]

Hi Fred,

thank you, it works!!

Bye
Albert

2018-02-16 11:47 GMT+01:00 Fred Toussi via hsqldb-developers <
hsq...@li...>:

> HSQLDB returns Object[] in this case. So you should be able to write:
>
> a=statement.getArray();
> Object[] zips = a.getArray();
>
> each element of the zips array is a String.
>
> Fred
>
> On Fri, Feb 16, 2018, at 10:32, ZomB_ wrote:
> > Hallo hsqldb developers,
> >
> > how can i access the OUT array elements from the procedure call?
> > Here is my procedure:
> > --
> > CREATE PROCEDURE prc_test_varray
> >   (
> >     OUT po_id VARCHAR(30) ARRAY
> >
> >   )
> > READS SQL DATA
> > BEGIN ATOMIC
> > DECLARE ids VARCHAR(30) ARRAY DEFAULT ARRAY[];
> >  SET ids[1] = 'HSQL';
> >  SET ids[2] = 'FAST';
> >  SET ids[3] = 'FASTER';
> >  SET po_id = ids;
> > END;
> > --
> > Here is java procedure call:
> > ...
> > CallableStatement stmt = null;
> >               Array a = null;
> >               try {
> >                       conn = util.getHsqlConnection();
> >                       String sql = "call prc_test_varray(?);";
> >                       stmt = conn.prepareCall(sql);
> >                       stmt.registerOutParameter(1,java.sql.Types.ARRAY);
> >                       stmt.execute();
> >                       a=stmt.getArray(1);
> >                       log.debug("Value {}, Typ: {}", a,
> a.getBaseTypeName());
> >                       String[] zips = (String[])a.getArray();
> >                   for (int i = 0; i < zips.length; i++) {
> >                               log.debug("Element",(zips[i]));
> >                   }
> >
> >               }
> > ...
> >
> > Here is debug out with exception:
> > 11:20:30.673 [main] DEBUG de.db.Start - Value
> ARRAY['HSQL','FAST','FASTER'],
> > Typ: VARCHAR
> > java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to
> > [Ljava.lang.String;11:20:30.675 [main] ERROR de.db.Start -
> > java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to
> > [Ljava.lang.String;
> >
> >       at de.db.Start.sel_arr(Start.java:68)
> >       at de.db.Start.main(Start.java:23)
> >
> >
> > Thanks for any help.
> >
> > Bye
> > Albert
> >
> >
> >
> > --
> > Sent from: http://hsqldb.10974.n7.nabble.com/HSQLDB-Dev-f3585.html
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > hsqldb-developers mailing list
> > hsq...@li...
> > https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>

Re: [Hsqldb-developers] OUT VALUE on Stored Procedures

[Fred T. <fr...@us...>]

HSQLDB returns Object[] in this case. So you should be able to write:

a=statement.getArray();
Object[] zips = a.getArray();

each element of the zips array is a String.

Fred

On Fri, Feb 16, 2018, at 10:32, ZomB_ wrote:
> Hallo hsqldb developers,
> 
> how can i access the OUT array elements from the procedure call?
> Here is my procedure:
> --
> CREATE PROCEDURE prc_test_varray
>   (
>     OUT po_id VARCHAR(30) ARRAY 
>     
>   )
> READS SQL DATA  
> BEGIN ATOMIC
> DECLARE ids VARCHAR(30) ARRAY DEFAULT ARRAY[];
>  SET ids[1] = 'HSQL';
>  SET ids[2] = 'FAST';
>  SET ids[3] = 'FASTER';
>  SET po_id = ids;
> END;
> --
> Here is java procedure call:
> ...
> CallableStatement stmt = null;
> 		Array a = null;
> 		try {
> 			conn = util.getHsqlConnection();
> 			String sql = "call prc_test_varray(?);";
> 			stmt = conn.prepareCall(sql);
> 			stmt.registerOutParameter(1,java.sql.Types.ARRAY);
> 			stmt.execute();
> 			a=stmt.getArray(1);
> 			log.debug("Value {}, Typ: {}", a, a.getBaseTypeName());
> 			String[] zips = (String[])a.getArray();
> 		    for (int i = 0; i < zips.length; i++) {
> 		        	log.debug("Element",(zips[i]));
> 		    }
> 			
> 		}
> ...
> 
> Here is debug out with exception:
> 11:20:30.673 [main] DEBUG de.db.Start - Value ARRAY['HSQL','FAST','FASTER'],
> Typ: VARCHAR
> java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to
> [Ljava.lang.String;11:20:30.675 [main] ERROR de.db.Start -
> java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to
> [Ljava.lang.String;
> 
> 	at de.db.Start.sel_arr(Start.java:68)
> 	at de.db.Start.main(Start.java:23)
> 
> 
> Thanks for any help.
> 
> Bye
> Albert
> 
> 
> 
> --
> Sent from: http://hsqldb.10974.n7.nabble.com/HSQLDB-Dev-f3585.html
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

[Hsqldb-developers] OUT VALUE on Stored Procedures

[ZomB_ <alb...@gm...>]

Hallo hsqldb developers,

how can i access the OUT array elements from the procedure call?
Here is my procedure:
--
CREATE PROCEDURE prc_test_varray
  (
    OUT po_id VARCHAR(30) ARRAY 
    
  )
READS SQL DATA  
BEGIN ATOMIC
DECLARE ids VARCHAR(30) ARRAY DEFAULT ARRAY[];
 SET ids[1] = 'HSQL';
 SET ids[2] = 'FAST';
 SET ids[3] = 'FASTER';
 SET po_id = ids;
END;
--
Here is java procedure call:
...
CallableStatement stmt = null;
		Array a = null;
		try {
			conn = util.getHsqlConnection();
			String sql = "call prc_test_varray(?);";
			stmt = conn.prepareCall(sql);
			stmt.registerOutParameter(1,java.sql.Types.ARRAY);
			stmt.execute();
			a=stmt.getArray(1);
			log.debug("Value {}, Typ: {}", a, a.getBaseTypeName());
			String[] zips = (String[])a.getArray();
		    for (int i = 0; i < zips.length; i++) {
		        	log.debug("Element",(zips[i]));
		    }
			
		}
...

Here is debug out with exception:
11:20:30.673 [main] DEBUG de.db.Start - Value ARRAY['HSQL','FAST','FASTER'],
Typ: VARCHAR
java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to
[Ljava.lang.String;11:20:30.675 [main] ERROR de.db.Start -
java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to
[Ljava.lang.String;

	at de.db.Start.sel_arr(Start.java:68)
	at de.db.Start.main(Start.java:23)


Thanks for any help.

Bye
Albert



--
Sent from: http://hsqldb.10974.n7.nabble.com/HSQLDB-Dev-f3585.html

Re: [Hsqldb-developers] Error accessing DB

[Fred T. <fr...@us...>]

This might happen in situations where files were not saved properly on
client machines due to disk error, disk full or whatever.
You need to have a backup strategy to revert to a good version if
this happens.
You can also get paid support from http://hyperxtreme.co.uk for data
recovery and repair.
Fred


On Fri, Oct 20, 2017, at 14:45, Alexander Gerbig wrote:
> Hello HSQL developers,
> 
> we use a hsqldb for the local storage of data in a client application.
> Some users report, that they cannot access their database. They get
> the following error:> 
> _java.sql.SQLException_: No suitable driver found for jdbc:hsqldb:file:<url-to-
> db>> 
> This exception comes from eclipse link that we use to access the
> database. Accessing the database with plain jdbc shows the
> following error:> 
> Caused by: org.hsqldb.HsqlException: error in script file line: 71 <path-to-
> db> IO error: RowInputBinary 6341 in statement [SET TABLE
> PUBLIC.KONTAKT INDEX '6341 0 482']> at org.hsqldb.error.Error.error(Unknown Source)
> at org.hsqldb.scriptio.ScriptReaderText.readDDL(Unknown Source)
> at org.hsqldb.scriptio.ScriptReaderBase.readAll(Unknown Source)
> at org.hsqldb.persist.Log.processScript(Unknown Source)
> at org.hsqldb.persist.Log.open(Unknown Source)
> at org.hsqldb.persist.Logger.open(Unknown Source)
> at org.hsqldb.Database.reopen(Unknown Source)
> at org.hsqldb.Database.open(Unknown Source)
> at org.hsqldb.DatabaseManager.getDatabase(Unknown Source)
> at org.hsqldb.DatabaseManager.newSession(Unknown Source)
> ... 4 more
> Caused by: org.hsqldb.HsqlException: IO error: RowInputBinary 6341
> at org.hsqldb.error.Error.error(Unknown Source)
> at org.hsqldb.rowio.RowInputBinary.readString(Unknown Source)
> at org.hsqldb.rowio.RowInputBinary.readChar(Unknown Source)
> at org.hsqldb.rowio.RowInputBase.readData(Unknown Source)
> at org.hsqldb.rowio.RowInputBinary.readData(Unknown Source)
> at org.hsqldb.rowio.RowInputBase.readData(Unknown Source)
> at org.hsqldb.rowio.RowInputBinary.readData(Unknown Source)
> at org.hsqldb.rowio.RowInputBinaryDecode.readData(Unknown Source)
> at org.hsqldb.RowAVLDisk.<init>(Unknown Source)
> at org.hsqldb.persist.RowStoreAVLDisk.get(Unknown Source)
> at org.hsqldb.persist.DataFileCache.getFromFile(Unknown Source)
> at org.hsqldb.persist.DataFileCache.get(Unknown Source)
> at org.hsqldb.persist.RowStoreAVLDisk.get(Unknown Source)
> at org.hsqldb.persist.RowStoreAVLDisk.setAccessor(Unknown Source)
> at org.hsqldb.Table.setIndexRoots(Unknown Source)
> at org.hsqldb.Table.setIndexRoots(Unknown Source)
> at org.hsqldb.StatementCommand.getResult(Unknown Source)
> at org.hsqldb.StatementCommand.execute(Unknown Source)
> at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
> ... 13 more
> Caused by: java.io.UTFDataFormatException
> at org.hsqldb.lib.StringConverter.readUTF(Unknown Source)
> at org.hsqldb.lib.StringConverter.readUTF(Unknown Source)
> ... 31 more
> 
> We use HSQLDB in Version 2.3.4 with eclipse link in Version 2.6.0. We
> open the database with the following properties:> 
> url: jdbc:hsqldb:file:${path-to-
> db};shutdown=true;hsqldb.default_table_type=cached;crypt_key=${crypt-
> key};crypt_type=blowfish;crypt_lobs=true> hsqldb.lob_compressed: true"
> hsqldb.defrag_limit: 10
> 


> hsqldb.lob_file_scale:1
> 
> The database is encrypted which makes it hard to see what is wrong in
> the script file. Is there a way to repair this database?> 
> Any help is welcome.
> 
> Thanks.
> 
> Best regards,
> Alexander
> ----------------------------------------------------------------------
> --------> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _________________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

[Hsqldb-developers] Error accessing DB

[Alexander G. <ale...@gm...>]

Hello HSQL developers,

we use a hsqldb for the local storage of data in a client application. Some
users report, that they cannot access their database. They get the
following error:

java.sql.SQLException: No suitable driver found for
jdbc:hsqldb:file:<url-to-db>

This exception comes from eclipse link that we use to access the database.
Accessing the database with plain jdbc shows the following error:

Caused by: org.hsqldb.HsqlException: error in script file line: 71
<path-to-db> IO error: RowInputBinary 6341 in statement [SET TABLE
PUBLIC.KONTAKT INDEX '6341 0 482']
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.scriptio.ScriptReaderText.readDDL(Unknown Source)
at org.hsqldb.scriptio.ScriptReaderBase.readAll(Unknown Source)
at org.hsqldb.persist.Log.processScript(Unknown Source)
at org.hsqldb.persist.Log.open(Unknown Source)
at org.hsqldb.persist.Logger.open(Unknown Source)
at org.hsqldb.Database.reopen(Unknown Source)
at org.hsqldb.Database.open(Unknown Source)
at org.hsqldb.DatabaseManager.getDatabase(Unknown Source)
at org.hsqldb.DatabaseManager.newSession(Unknown Source)
... 4 more
Caused by: org.hsqldb.HsqlException: IO error: RowInputBinary 6341
at org.hsqldb.error.Error.error(Unknown Source)
at org.hsqldb.rowio.RowInputBinary.readString(Unknown Source)
at org.hsqldb.rowio.RowInputBinary.readChar(Unknown Source)
at org.hsqldb.rowio.RowInputBase.readData(Unknown Source)
at org.hsqldb.rowio.RowInputBinary.readData(Unknown Source)
at org.hsqldb.rowio.RowInputBase.readData(Unknown Source)
at org.hsqldb.rowio.RowInputBinary.readData(Unknown Source)
at org.hsqldb.rowio.RowInputBinaryDecode.readData(Unknown Source)
at org.hsqldb.RowAVLDisk.<init>(Unknown Source)
at org.hsqldb.persist.RowStoreAVLDisk.get(Unknown Source)
at org.hsqldb.persist.DataFileCache.getFromFile(Unknown Source)
at org.hsqldb.persist.DataFileCache.get(Unknown Source)
at org.hsqldb.persist.RowStoreAVLDisk.get(Unknown Source)
at org.hsqldb.persist.RowStoreAVLDisk.setAccessor(Unknown Source)
at org.hsqldb.Table.setIndexRoots(Unknown Source)
at org.hsqldb.Table.setIndexRoots(Unknown Source)
at org.hsqldb.StatementCommand.getResult(Unknown Source)
at org.hsqldb.StatementCommand.execute(Unknown Source)
at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
... 13 more
Caused by: java.io.UTFDataFormatException
at org.hsqldb.lib.StringConverter.readUTF(Unknown Source)
at org.hsqldb.lib.StringConverter.readUTF(Unknown Source)
... 31 more

We use HSQLDB in Version 2.3.4 with eclipse link in Version 2.6.0. We open
the database with the following properties:

url: jdbc:hsqldb:file:${path-to-db};shutdown=true;hsqldb.default_table_type=cached;crypt_key=${crypt-key};crypt_type=blowfish;crypt_lobs=true
hsqldb.lob_compressed: true"
hsqldb.defrag_limit: 10

hsqldb.lob_file_scale:1

The database is encrypted which makes it hard to see what is wrong in the
script file. Is there a way to repair this database?

Any help is welcome.

Thanks.

Best regards,
Alexander

Re: [Hsqldb-developers] Lobs file size

[Fred T. <fr...@us...>]

You can open a bug report if you wish.

The space for temporary lobs is reclaimed at each checkpoint and is reused for future lobs.
It is not possible to reduce the size of the lobs file. There is a procedure in HyperXtremeSQL for this, but not in HSQLDB.
Fred


On Tue, Jul 18, 2017, at 16:05, Alexander Gerbig wrote:
> Hi Fred,
> 
> because of the following reasons we consider this as a bug:
> - the upper copy of the clob is not removed afterwards and the already occupied space is not reused> - it is not easily possible to reduce the size of the lobs-file
> - this behavior is not documented
> 
> Therefore I will open a bug in the Bug Tracker.
> 
> Bye, Alex
> 
> 
> 2017-07-13 19:31 GMT+02:00 Alexander Gerbig <ale...@gm...>:>> Ok, thank you. Is it possible to reduce the size of the file again?
>> 
>> 
>> > Am 13.07.2017 um 18:08 schrieb Fred Toussi via hsqldb-developers <hsq...@li...>:>>  >
>>  > This is normal. An uppercase copy of the CLOB  is created. To avoid it,>>  > cast the CLOB to VARCHAR before converting to uppercase.
>>  >
>>  > Fred Toussi
>>  >
>>  >> On Thu, Jul 13, 2017, at 10:52, Alexander Gerbig wrote:
>>  >> Hallo hsqldb developers,
>>  >>
>>  >> we use a hsqldb in our application an experience a strange behavior. We>>  >> have some clob columns in different tables and when we execute an select>>  >> with an upper on the clob column in a where clause the lobs file>>  >> increases in size. Is it a very practice to make an upper on an clob>>  >> column? Is this normal?
>>  >>
>>  >> Thanks for any help.
>>  >>
>>  >> Bye
>>  >> Alex
>>  >> ------------------------------------------------------------------------------>>  >> Check out the vibrant tech community on one of the world's most
>>  >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>  >> _______________________________________________
>>  >> hsqldb-developers mailing list
>>  >> hsq...@li...
>>  >> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>>  >
>>  > ------------------------------------------------------------------------------>>  > Check out the vibrant tech community on one of the world's most
>>  > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>  > _______________________________________________
>>  > hsqldb-developers mailing list
>>  > hsq...@li...
>>  > https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
> ------------------------------------------------------------------------------> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _________________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

Re: [Hsqldb-developers] Lobs file size

[Alexander G. <ale...@gm...>]

Hi Fred,

because of the following reasons we consider this as a bug:
- the upper copy of the clob is not removed afterwards and the already
occupied space is not reused
- it is not easily possible to reduce the size of the lobs-file
- this behavior is not documented

Therefore I will open a bug in the Bug Tracker.

Bye, Alex


2017-07-13 19:31 GMT+02:00 Alexander Gerbig <ale...@gm...>:

> Ok, thank you. Is it possible to reduce the size of the file again?
>
> > Am 13.07.2017 um 18:08 schrieb Fred Toussi via hsqldb-developers <
> hsq...@li...>:
> >
> > This is normal. An uppercase copy of the CLOB  is created. To avoid it,
> > cast the CLOB to VARCHAR before converting to uppercase.
> >
> > Fred Toussi
> >
> >> On Thu, Jul 13, 2017, at 10:52, Alexander Gerbig wrote:
> >> Hallo hsqldb developers,
> >>
> >> we use a hsqldb in our application an experience a strange behavior. We
> >> have some clob columns in different tables and when we execute an select
> >> with an upper on the clob column in a where clause the lobs file
> >> increases in size. Is it a very practice to make an upper on an clob
> >> column? Is this normal?
> >>
> >> Thanks for any help.
> >>
> >> Bye
> >> Alex
> >> ------------------------------------------------------------
> ------------------
> >> Check out the vibrant tech community on one of the world's most
> >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >> _______________________________________________
> >> hsqldb-developers mailing list
> >> hsq...@li...
> >> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > hsqldb-developers mailing list
> > hsq...@li...
> > https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>

Re: [Hsqldb-developers] Lobs file size

[Alexander G. <ale...@gm...>]

Ok, thank you. Is it possible to reduce the size of the file again?

> Am 13.07.2017 um 18:08 schrieb Fred Toussi via hsqldb-developers <hsq...@li...>:
> 
> This is normal. An uppercase copy of the CLOB  is created. To avoid it,
> cast the CLOB to VARCHAR before converting to uppercase.
> 
> Fred Toussi
> 
>> On Thu, Jul 13, 2017, at 10:52, Alexander Gerbig wrote:
>> Hallo hsqldb developers,
>> 
>> we use a hsqldb in our application an experience a strange behavior. We
>> have some clob columns in different tables and when we execute an select
>> with an upper on the clob column in a where clause the lobs file
>> increases in size. Is it a very practice to make an upper on an clob
>> column? Is this normal?
>> 
>> Thanks for any help.
>> 
>> Bye
>> Alex
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> hsqldb-developers mailing list
>> hsq...@li...
>> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

Re: [Hsqldb-developers] Lobs file size

[Fred T. <fr...@us...>]

This is normal. An uppercase copy of the CLOB  is created. To avoid it,
cast the CLOB to VARCHAR before converting to uppercase.

Fred Toussi

On Thu, Jul 13, 2017, at 10:52, Alexander Gerbig wrote:
> Hallo hsqldb developers,
> 
> we use a hsqldb in our application an experience a strange behavior. We
> have some clob columns in different tables and when we execute an select
> with an upper on the clob column in a where clause the lobs file
> increases in size. Is it a very practice to make an upper on an clob
> column? Is this normal?
> 
> Thanks for any help.
> 
> Bye
> Alex
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

[Hsqldb-developers] Lobs file size

[Alexander G. <ale...@gm...>]

Hallo hsqldb developers,

we use a hsqldb in our application an experience a strange behavior. We have some clob columns in different tables and when we execute an select with an upper on the clob column in a where clause the lobs file increases in size. Is it a very practice to make an upper on an clob column? Is this normal?

Thanks for any help.

Bye
Alex

Re: [Hsqldb-developers] How to run the tests?

[Maurício A. <mau...@gm...>]

Hi Fred,

Oh, thanks!

I manage to execute most tests now, by creating a /hsql/tests folder on my
Mac. Most of tests are passing now; some of them are still red and I need
to investigate a bit more.

More importantly, with the ones that I managed to execute, I already found
a breaking change in our hsqldb version! That's a win! :)

Cheers,

On Sun, Dec 25, 2016 at 1:57 PM Fred Toussi <fr...@us...>
wrote:

> Merry Xmas to you.
>
> I read you blog on TDD and found it interesting.
>
> This test does not fail when I run it. The file: database for this test is
> deleted at the start of each of the two tests that use it and is shutdown
> at the end. Perhaps your version of JUnit is running the tests in parallel.
> The reported error means a second processes is attempting to open an
> already open file database.
>
> This test is actually a demonstration of an old issue that was fixed at
> the time and could be considered a regression test for the syntax of the
> statements but not for the results (which needs visual inspection of the
> output).
>
> Some JUnit tests in that directory extend TestBase and some don't. The
> ones that don't are more likely to be demos for issues like this one.
>
>
> Fred
>
> On Sun, Dec 25, 2016, at 11:35, Maurício Aniche wrote:
>
> And should I make anything to make them all pass? As an example,
> TestDatetimeSimple#testSimple fails (database lock acquisition failure...).
>
> Merry xmas, Fred!
>
> Cheers,
>
> On Sat, Dec 24, 2016 at 12:16 PM Fred Toussi <fr...@us...>
> wrote:
>
> There are several groups of tests.
>
> The JUnit test for individual classes are in the test-src directory. Those
> for database features are in the src directory in the org.hsqldb.test
> package.
>
> There are some non-Junit tests that need their output to be checked and
> compared to previous runs. These are in the org.hsqldb.test package. The
> main group consists of multiple scripts in the testrun directory. The
> scripts are run by the org.hsqldb.test.TestScripts class.
>
> Fred Toussi
>
> On Fri, Dec 23, 2016, at 20:17, Maurício Aniche wrote:
>
> Hi team,
>
> We are using HSQLDB in one of our research projects. We are currently able
> to manually compile it, but not able to run the tests.
>
> Is there a guide on how to do it?
>
> Merry xmas!
>
> --
> Maurício Aniche
> Postdoc researcher
> Delft University of Technology
> www.mauricioaniche.com
> @mauricioaniche
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> *_______________________________________________*
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>
> --
> Maurício Aniche
> Postdoc researcher
> Delft University of Technology
> www.mauricioaniche.com
> @mauricioaniche
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> *_______________________________________________*
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>
-- 
Maurício Aniche
Postdoc researcher
Delft University of Technology
www.mauricioaniche.com
@mauricioaniche

Re: [Hsqldb-developers] How to run the tests?

[Fred T. <fr...@us...>]

Merry Xmas to you.

 

I read you blog on TDD and found it interesting.

 

This test does not fail when I run it. The file: database for this test
is deleted at the start of each of the two tests that use it and is
shutdown at the end. Perhaps your version of JUnit is running the tests
in parallel. The reported error means a second processes is attempting
to open an already open file database.
 

This test is actually a demonstration of an old issue that was fixed at
the time and could be considered a regression test for the syntax of
the statements but not for the results (which needs visual inspection
of the output).
 

Some JUnit tests in that directory extend TestBase and some don't. The
ones that don't are more likely to be demos for issues like this one.
 

 

Fred

 

On Sun, Dec 25, 2016, at 11:35, Maurício Aniche wrote:

> And should I make anything to make them all pass? As an example,
> TestDatetimeSimple#testSimple fails (database lock acquisition
> failure...).
>  
>  Merry xmas, Fred!


>  

> Cheers,
>   


> On Sat, Dec 24, 2016 at 12:16 PM Fred Toussi
> <fr...@us...> wrote:
>> There are several groups of tests.

>>  

>> The JUnit test for individual classes are in the test-src directory.
>> Those for database features are in the src directory in the
>> org.hsqldb.test package.
>>  

>> There are some non-Junit tests that need their output to be
>> checked and compared to previous runs. These are in the
>> org.hsqldb.test package. The main group consists of multiple
>> scripts in the testrun directory. The scripts are run by the
>> org.hsqldb.test.TestScripts class.
>>  

>> Fred Toussi

>>  

>> On Fri, Dec 23, 2016, at 20:17, Maurício Aniche wrote:

>>> Hi team,

>>>  

>>> We are using HSQLDB in one of our research projects. We are
>>> currently able to manually compile it, but not able to run the
>>> tests.
>>>  

>>> Is there a guide on how to do it?

>>>  

>>> Merry xmas!

>>>  

>>> --

>>> Maurício Aniche

>>> Postdoc researcher

>>> Delft University of Technology

>>> www.mauricioaniche.com

>>> @mauricioaniche

>>> --------------------------------------------------------------------
>>> ----------
>>> Developer Access Program for Intel Xeon Phi Processors

>>> Access to Intel Xeon Phi processor-based developer platforms.

>>> With one year of Intel Parallel Studio XE.

>>> Training and support from Colfax.

>>> Order your platform today.http://sdm.link/intel

>>> _________________________________________________

>>> hsqldb-developers mailing list

>>> hsq...@li...

>>> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>>  --------------------------------------------------------------------
>>  ----------
>>  Developer Access Program for Intel Xeon Phi Processors Access to
>>  Intel Xeon Phi processor-based developer platforms. With one year of
>>  Intel Parallel Studio XE. Training and support from Colfax. Order
>>  your platform today.
>>  http://sdm.link/intel_______________________________________________
>>  hsqldb-developers mailing list hsqldb-
>>  dev...@li...
>>  https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
> --

> Maurício Aniche

> Postdoc researcher

> Delft University of Technology

> www.mauricioaniche.com

> @mauricioaniche

> ----------------------------------------------------------------------
> --------
> Developer Access Program for Intel Xeon Phi Processors

> Access to Intel Xeon Phi processor-based developer platforms.

> With one year of Intel Parallel Studio XE.

> Training and support from Colfax.

> Order your platform today.http://sdm.link/intel

> _________________________________________________

> hsqldb-developers mailing list

> hsq...@li...

> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers

Re: [Hsqldb-developers] How to run the tests?

[Maurício A. <mau...@gm...>]

And should I make anything to make them all pass? As an example,
TestDatetimeSimple#testSimple fails (database lock acquisition failure...).

Merry xmas, Fred!

Cheers,

On Sat, Dec 24, 2016 at 12:16 PM Fred Toussi <fr...@us...>
wrote:

> There are several groups of tests.
>
> The JUnit test for individual classes are in the test-src directory. Those
> for database features are in the src directory in the org.hsqldb.test
> package.
>
> There are some non-Junit tests that need their output to be checked and
> compared to previous runs. These are in the org.hsqldb.test package. The
> main group consists of multiple scripts in the testrun directory. The
> scripts are run by the org.hsqldb.test.TestScripts class.
>
> Fred Toussi
>
> On Fri, Dec 23, 2016, at 20:17, Maurício Aniche wrote:
>
> Hi team,
>
> We are using HSQLDB in one of our research projects. We are currently able
> to manually compile it, but not able to run the tests.
>
> Is there a guide on how to do it?
>
> Merry xmas!
>
> --
> Maurício Aniche
> Postdoc researcher
> Delft University of Technology
> www.mauricioaniche.com
> @mauricioaniche
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> *_______________________________________________*
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> _______________________________________________
> hsqldb-developers mailing list
> hsq...@li...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
>
-- 
Maurício Aniche
Postdoc researcher
Delft University of Technology
www.mauricioaniche.com
@mauricioaniche