This issue is very consistently happening when the process is close to
using its heap limit. Perhaps there is some OutOfMemory error being
suppressed?
On Thursday, May 22, 2014 11:45:20 AM UTC-4, Thomas Mueller wrote:
Hi,
You could export the database to a script file, and then create a
On 2014-05-27 20:51, san...@zeroturnaround.com wrote:
So what do you think.. something that could be improved here? H2 seems to spend
most of its time in places like
TreeCurson.next() and other index-related methods. Just a wild guess: maybe it
is recalculating some index a million
times
On 2014-05-27 17:24, Adam McMahon wrote:
I would like to use the Clob data type for my variable length strings that
average around 300 characters. I see in the
doc that I should use |PreparedStatement.setCharacterStream| to store
values. Instead I am simply using
The console history is a nice feature, but sometimes I get kicked out and
have to log in again and the history is gone.
I don't know exactly when and why I get kicked out. Is there something I
could do about it?
I didn't mean the persistency literarily, it's just that I'd love if it
could
Sounds reasonable to me.
The code you want lives in
src\main\org\h2\server\web\WebApp.java
src\main\org\h2\server\web\WebSession.java
search for @history and follow the code.
I suspect that the easiest option would be to have the console webapp store the history data using the
Same problem.
1.
The database was created in CREATE_BUILD 170, then was used with 1.3.174.
I've tried using 1.4.178 on that database in Hibernate-based product - got
org.h2.jdbc.JdbcSQLException: Unique index or primary key violation:
PRIMARY KEY ON .PAGE_INDEX; SQL statement:[...]
1.3.175
Hi,
The H2 Console tool stores the settings in a file called
.h2.server.properties in the current user home directory
(Constants.SERVER_PROPERTIES_NAME). If the history is stored, it should
probably be stored there. But I'm not sure whether it should be stored; it
would be a security problem
On Wed, May 28, 2014 at 8:13 PM, Thomas Mueller
thomas.tom.muel...@gmail.com wrote:
Hi,
The H2 Console tool stores the settings in a file called
.h2.server.properties in the current user home directory
(Constants.SERVER_PROPERTIES_NAME).
I'd also prefer Properties to Preferences, as
How can I set the cache for a primary key sequence? I haven't found a way
to specify the cache when creating the column. Also haven't found a way to
specify the sequence for the column, so I can't create the sequence with
the right cache and then create a column that uses it.
Also, the alter
I updated from 1.3.171 to 1.3.176 to pick up the alter sequence .. cache
command. After changing the cache, on the next start of the app h2 is
unable to connect to the db. It fills the trace file with this:
05-28 17:27:33 database: ALTER TABLE PUBLIC.PROBES ADD CONSTRAINT
With much digging through the archives, I found this example for setting
the sequence when creating a table:
CREATE SEQUENCE TESTSEQ;
CREATE TABLE TEST(ID INT DEFAULT NEXT VALUE FOR TESTSEQ PRIMARY KEY);
However I still have no migration strategy due to the problems moving from
171 to 176.
On
11 matches
Mail list logo
