[h2] is not null <-- not working
Hi is not null <-- not working, but is not 'null' <-- this working. May I know why? thanks from Peter (cmk...@hotmail.com) -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] 1.4 beta creates much bigger database file
I have replaced by BLOB columns by BINARY(32000) ones (more than enough in
our case). After exporting the database in SQL ('script' command),
recreating a blank database and reimporting the SQL ('runscript'), I went
from 1.7 Gb to 17 Mb.
I'll monitor the database in the next days to see if the inflation starts
again.
Damien.
On Monday, 2 February 2015 17:40:49 UTC+1, Damien Coraboeuf wrote:
>
> Hi,
>
> Speaking of real world example - we are using H2 1.4.x to hold results for
> a continuous delivery chain. With 1.4.177, our database was > 600 Mb, and
> after a 'shutdown defrag', we went down to... 11 Mb. We switched to 1.4.184
> but now, the database has grown up to 1.7 Gb. That's a serious issue for us
> :(
>
> The URL we use is:
>
> jdbc:h2:/opt/ontrack/database/data;MODE=MYSQL
>
> Damien.
>
> On Monday, 5 January 2015 18:15:56 UTC+1, Thomas Mueller wrote:
>>
>> Hi,
>>
>> OK, that's nice! There is still quite a lot of room for improvements, and
>> I don't consider this completely fixed, but will not work on it with very
>> high priority any longer.
>>
>> Regards,
>> Thomas
>>
>>
>> On Sunday, December 21, 2014, Steve McLeod wrote:
>>
>>> Hi Thomas,
>>>
>>> The database file size in 1.4.184 is much, much better than in earlier
>>> 1.4.x releases.
>>>
>>> I've done some trials and these are my findings:
>>>
>>> 1.3.176: Fully loaded database after shutdown is 317 Mb
>>> 1.4.184: Fully loaded database after shutdown is 380 Mb
>>>
>>> This seems reasonable.
>>>
>>>
>>> On Friday, 19 December 2014 17:15:29 UTC+8, Thomas Mueller wrote:
Hi,
Version 1.4.184 should produce smaller database files than previous
version (1.4.x - 1.4.182), maybe half or a third of the old file size. It
would be great to get some real-world results!
Regards,
Thomas
On Tue, May 6, 2014 at 6:24 PM, Thomas Mueller
wrote:
>
> Hi,
>
> Some initial results: you can shrink the database by running "shutdown
> compact" or "shutdown defrag". Each time this is run, it shrinks a few MB
> (up to some point, of course). This works, but it's relatively slow. Now
> the task is to make it faster. There are two ways: shrink it fully to the
> minimum size, and shrink it incrementally (like now) but faster. I'm
> working on that now.
>
> Regards,
> Thomas
>
>
>
> On Tue, May 6, 2014 at 11:39 AM, Steve McLeod
> wrote:
>
>> Hi Thomas,
>>
>> I've sent you a private email with a link to the new database file,
>> made with H2 1.4.178
>>
>> Regards,
>>
>> Steve
>>
>>
>> On Monday, 5 May 2014 07:46:16 UTC+2, Thomas Mueller wrote:
>>
>>> Hi,
>>>
>>> The database file should shrink if you run "shutdown defrag".
>>>
>>> The current compact algorithm is quite inefficient, that means the
>>> databases file is quite big on average. The highest priority is still
>>> to
>>> ensure it always works correctly, and when that's done I will work on
>>> more
>>> efficiently re-using disk space and specially compact the file faster
>>> when
>>> closing the database.
>>>
>>> Could you send me the new database file? It would be nice to have a
>>> real-world database file to test this. The last file you sent helped a
>>> lot,
>>> thanks to it I found some problems that completely prevented the file
>>> to
>>> shrink.
>>>
>>> Regards,
>>> Thomas
>>>
>>>
>>>
>>> On Sunday, May 4, 2014, Steve McLeod wrote:
>>>
Hi Thomas,
I tested the same large data import with H2 1.4.178, and there is
no improvement over H2 1.4.177.
Here are the file sizes, in both cases after the app has stopped:
H2 1.3.176: pokercopilot.h2.db 301,669,352 bytes
H2 1.4.178: pokercopilot.mv.db 1,023,037,440 bytes
Let me know what I can do to help.
Regards,
Steve
On Saturday, 19 April 2014 11:44:05 UTC+2, Steve McLeod wrote:
Hi Thomas,
Great! Glad I could help make your superb product even better.
On Friday, 18 April 2014 21:38:27 UTC+2, Thomas Mueller wrote:
Hi,
Thanks a lot for the database! I know what the problem is now, but
I couldn't fix it yet. The database file (pokercopilot2.mv.db) has
about
181 MB of "live" data, the rest (about 78%) is not used. The mechanism
to
get rid of the unused space is not working as it should for this case
(I
think the problem is that b-tree nodes are not processed correctly).
This
will be fixed in the next release.
Regards,
Thomas
On Fri,
Re: [h2] 1.4 beta creates much bigger database file
Hi, Speaking of real world example - we are using H2 1.4.x to hold results for a continuous delivery chain. With 1.4.177, our database was > 600 Mb, and after a 'shutdown defrag', we went down to... 11 Mb. We switched to 1.4.184 but now, the database has grown up to 1.7 Gb. That's a serious issue for us :( The URL we use is: jdbc:h2:/opt/ontrack/database/data;MODE=MYSQL Damien. On Monday, 5 January 2015 18:15:56 UTC+1, Thomas Mueller wrote: > > Hi, > > OK, that's nice! There is still quite a lot of room for improvements, and > I don't consider this completely fixed, but will not work on it with very > high priority any longer. > > Regards, > Thomas > > > On Sunday, December 21, 2014, Steve McLeod > wrote: > >> Hi Thomas, >> >> The database file size in 1.4.184 is much, much better than in earlier >> 1.4.x releases. >> >> I've done some trials and these are my findings: >> >> 1.3.176: Fully loaded database after shutdown is 317 Mb >> 1.4.184: Fully loaded database after shutdown is 380 Mb >> >> This seems reasonable. >> >> >> On Friday, 19 December 2014 17:15:29 UTC+8, Thomas Mueller wrote: >>> >>> Hi, >>> >>> Version 1.4.184 should produce smaller database files than previous >>> version (1.4.x - 1.4.182), maybe half or a third of the old file size. It >>> would be great to get some real-world results! >>> >>> Regards, >>> Thomas >>> >>> >>> >>> On Tue, May 6, 2014 at 6:24 PM, Thomas Mueller >>> wrote: Hi, Some initial results: you can shrink the database by running "shutdown compact" or "shutdown defrag". Each time this is run, it shrinks a few MB (up to some point, of course). This works, but it's relatively slow. Now the task is to make it faster. There are two ways: shrink it fully to the minimum size, and shrink it incrementally (like now) but faster. I'm working on that now. Regards, Thomas On Tue, May 6, 2014 at 11:39 AM, Steve McLeod wrote: > Hi Thomas, > > I've sent you a private email with a link to the new database file, > made with H2 1.4.178 > > Regards, > > Steve > > > On Monday, 5 May 2014 07:46:16 UTC+2, Thomas Mueller wrote: > >> Hi, >> >> The database file should shrink if you run "shutdown defrag". >> >> The current compact algorithm is quite inefficient, that means the >> databases file is quite big on average. The highest priority is still to >> ensure it always works correctly, and when that's done I will work on >> more >> efficiently re-using disk space and specially compact the file faster >> when >> closing the database. >> >> Could you send me the new database file? It would be nice to have a >> real-world database file to test this. The last file you sent helped a >> lot, >> thanks to it I found some problems that completely prevented the file to >> shrink. >> >> Regards, >> Thomas >> >> >> >> On Sunday, May 4, 2014, Steve McLeod wrote: >> >>> Hi Thomas, >>> >>> I tested the same large data import with H2 1.4.178, and there is no >>> improvement over H2 1.4.177. >>> >>> Here are the file sizes, in both cases after the app has stopped: >>> >>> H2 1.3.176: pokercopilot.h2.db 301,669,352 bytes >>> H2 1.4.178: pokercopilot.mv.db 1,023,037,440 bytes >>> >>> Let me know what I can do to help. >>> >>> Regards, >>> >>> Steve >>> >>> >>> On Saturday, 19 April 2014 11:44:05 UTC+2, Steve McLeod wrote: >>> >>> Hi Thomas, >>> >>> Great! Glad I could help make your superb product even better. >>> >>> >>> >>> On Friday, 18 April 2014 21:38:27 UTC+2, Thomas Mueller wrote: >>> >>> Hi, >>> >>> Thanks a lot for the database! I know what the problem is now, but I >>> couldn't fix it yet. The database file (pokercopilot2.mv.db) has about >>> 181 >>> MB of "live" data, the rest (about 78%) is not used. The mechanism to >>> get >>> rid of the unused space is not working as it should for this case (I >>> think >>> the problem is that b-tree nodes are not processed correctly). This >>> will be >>> fixed in the next release. >>> >>> Regards, >>> Thomas >>> >>> >>> On Fri, Apr 18, 2014 at 5:29 PM, Steve McLeod >>> wrote: >>> >>> Hi Thomas, >>> >>> I've sent a link to file privately to your email address. >>> >>> Regards, >>> >>> Steve >>> >>> >>> >>> On Friday, 18 April 2014 14:04:37 UTC+2, Thomas Mueller wrote: >>> >>> Hi, >>> >>> Hm, that didn't help much. Could you send me the (compressed) >>> database files please? If it's too big, what is the compressed size of >>> the >>> files? >>> >>> Regards, >>> Thomas >>> >>> >>> On Fri, Apr 18,
[h2] 1.4.x stability
Hi, we're using H2 1.3.176 to back up a 24/7 Play!-based application, average database size ~100 Mb, persisted to file system. We have some performance problems. I thus have a very general question - when do you think 1.4.x branch would be stable enough to end the beta, and how would you assess the stability right now? Would you recommend to update to the current latest beta, or rather not? Thanks a lot! -- Sander Sõnajalg ZeroTurnaround -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Missing "column" type in right-hand parameter in ConditionIn
Le 31/07/2014 18:04, Arnaud Thimel a écrit : > Hi, > > ( I'm new to the mailing-list, sorry if I do not follow the expectations. ) > > I'm using H2 1.3.176 together with Hibernate 4.3.6.Final. > I'm having a bug with a particular Hibernate query involving IN with an enum > list. [1] > > I thought Hibernate was involved in this issue, but it seems that it comes > from H2. > > You will find attached two tests in tests.java. > > The first one (testColumnMetaDataWithEquals) works fine. > It creates a PreparedStatement ( "SELECT ... WHERE someColumn = ?" ) then uses > "preparedStmt.getParameterMetaData().getParameterType(1)" which returns the > expected value. > > The second one (testColumnMetaDataWithIn) is doing exactly the same thing > except the WHERE clause is using IN ( "SELECT ... WHERE someColumn IN ( ? , ? > ) "). > Then "preparedStmt.getParameterMetaData().getParameterType(1)" does not return > the expected value. > > I wrote a patch for "ConditionIn" based on the "Comparison" source code. > This patch proposal is attached, please let me know if it is acceptable. > > Best regards, > Arnaud > > > [1] Is it off topic, but the Hibernate query looks like " FROM SomeEntity > WHERE someColumn IN ( :enum0 , :enum1 ) " Hi, Any news about this patch ? Regards. -- Éric Chatellier - www.codelutin.com - 02.40.50.29.28 -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Can't use h2 database in a thread only with Java 8
Le 09/12/2014 18:03, Thomas Mueller a écrit : > Hi, > > It looks like you are using "runscript" (RunScriptCommand in the stack trace). > Is this all you do in your program at that time (nothing is happening > concurrently)? If yes, could you post or send me the script file please? Hi I've tried to reproduce the bug in a test case with that script, but the error doesn't happen with only h2 and that script. Seams that this bug is a little bit tricky and may invlove connection pool and/or hibernate. Now that Java 8 is becoming main line, and i always experiencing this bug, i will investigate harder... -- Éric Chatellier - www.codelutin.com - 02.40.50.29.28 -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
