In the meantime I found out that the MAX_MEMORY_ROWS setting is accepted by the database (I've looked up the setting in the SETTINGS table of the information_schema).
So it seems that the behaviour described in this thread is not affected by the MAX_MEMORY_ROWS settings and therefore the workaround does not work. Noel, can you please check that? Thanks! Uli -- 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.