Personally, I'd say the easiest solution is to copy the CREATE ALIAS
syntax, so that we could say
CREATE TABLE TEST(ID int) ENGINE $$new MyEngine(val1, val2)$$
But Thomas might have a better idea.
On 2013-05-29 22:08, Andrew Franklin wrote:
I have written a custom TableEngine implementation
On 2013-05-30 00:34, Jason Pell wrote:
We finally got sick of this issue and migrated to HSQLDB for MVCC and
no more missing lob issues. We still use H2, but only for storing
configuration stuff that does not need to be updated concurrently.
It's a shame more attention has not been shown to
Network problems are always a pain.
You could try using Wireshark or Microsoft Network Monitor to capture
the connection, that might provide some more information.
You aren't by any chance using some kind of Connection Pool are you?
Some of those have timeout logic in them to kill off stale
Hi,
Let's concentrate on current use cases. I wouldn't want to implement a
feature that _might_ be useful in the future (do you know the term YAGNI?).
The path on disk, isn't it just the path of the database? Is the path
different for each table in a database? What are the other arguments you
I can't argue with you there, and I can understand that this one is a
difficult problem, but from what I have read it's been around a while and
still is an open problem.
I find it strange that more attention has not been paid to it is all.
On Thursday, May 30, 2013 4:30:41 PM UTC+10, Noel
I'm using MVCC and the only problems I've come across appear to be with
LOBS (that's ok for me, don't really need them for my use case).
What I mean is that it may have been less work for you to try and fix
the H2 source (Seeing the issues seem to all be with LOBS) rather than
change to
On 2013-05-30 08:48, Ryan How wrote:
And it is getting lots of attention, the entire file store is being
re-written to accommodate for MVCC right from the start!, that is why
they haven't been giving attention to maintaining the current
experimental MVCC mode (Please correct me if I am
On 2013-05-30 08:42, Jason Pell wrote:
I find it strange that more attention has not been paid to it is all.
Mostly because most of us don't use it, we find the normal mode to be
pretty peachy.
Now, I have noticed that over the last year various people have bumped
into locking issues, some
Hi Noel,
No, I don't think so. I'm checking the LibreOffice Base - Connections
settings and I have the Connection pooling enabled unchecked... however,
since you mention it... would it be a good idea to have checked instead?
But then which driver would I select? the JDBCDriver?
Note:
On 2013-05-30 09:28, Jorge Alberch wrote:
No, I don't think so. I'm checking the LibreOffice Base - Connections
settings and I have the Connection pooling enabled unchecked...
however, since you mention it... would it be a good idea to have
checked instead? But then which driver would I
I'd try the connection pooling :). I imagine that means it keeps a pool
of connections open to the database underneath, then when it needs a
connection in the GUI there is always one available.
I'd imagine the connection string would be the same, connection pooling
would be handled by
Hi,
I have a sample of h2 failing when used with spring integration jdbc
message channel store that times out on lock. Adding mvcc fixes that
particular problem. I will get a minimum test case that demonstrates this.
The real issue is by default h2 locks entire table so only one thread can
create table Company (id bigint generated by default as identity,location
bigint not null, addressId bigint, email varchar(255), name varchar(255),
phone1 varchar(255), phone2 varchar(255), primary key (id, location));
The above fails on H2 but runs on mysql
if i rewrite it as
create table
On 2013-05-30 10:56, jasonmp...@gmail.com wrote:
The real issue is by default h2 locks entire table so only one thread
can perform dml stuff this makes it unsuitable for our situation. And
we actually only use h2 in test we use Oracle or sql server in production
H2 is pretty fast, even with
Fixing the H2 source is easier said than done, changing to HSQLDB was
actually a few hours of work, granted they were a painful few hours, but
when
you use JPA and Hibernate, switching DB's is relatively painless.
We are still using H2 for a lot of stuff, even in production, we just use
We are doing integration testing using HSQLDB, we still do full blown
integration test with oracle, but on developers PC's Oracle XE is way too
heavy, so we have a local build which uses HSQLDB. This does do stuff that
requires reasonable concurrency from the DB and tends to cause timeouts
On 2013-05-30 12:58, Jason Pell wrote:
The row level locking is what we really needed and thus because MVCC
is experimental
with H2, we had to go with another DB where the MVCC support works
well with CLOB.
I doubt that. I suspect that you were just hitting some unfortunate
deadlocks in
We have tried this with the latest build but that did not solve the problem
for us. Any other advice on this one?
On Tuesday, 14 May 2013 10:51:06 UTC+5:30, Sanjeev Gour wrote:
Sorry, I mentioned the incorrect version number, I am using *1.3.168*.
Earlier we also tried without MVCC but that
Hi all,
we are using a H2 database (1.3.161) embedded in jboss 7.1.1.Final.
We wanted to cache the prepared queries but without caching the result of
it. Therefore we set OPTIMIZE_REUSE_RESULTS=0.
But unfortunately there is another reference-chain from the
PreparedStatement to its result. This
The way I see it, the TableEngine interface has the potential to enable
traditional SQL access to many NoSQL style stores, while removing the
burden of implementing a JDBC driver (and SQL parser) and enabling the
developer to concentrate on the much smaller task of the data to table
adapter
Hi,
Did you re-create the problematic index, or (even better) re-create the
database? To re-create the database, first create a SQL script using the
script to command, then create a new database, and run runscript.
Regards,
Thomas
On Thursday, May 30, 2013, Sanjeev Gour wrote:
We have tried
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/05/13 08:09, Noel Grandin wrote:
You could try running a CHECKPOINT SYNC command from onPause().
At the very least, that would dramatically reduce the amount of
work that H2 has to do during recovery.
To improve durability I've been
I have a table for witch after data is inserted, I need to do long running
proceeding from the data.
I plan to do the proceeding is a separate thread fired stared form the
trigger.
My question is, is it safe to send the connection sent to the trigger
(ether the init or the fire method) to the
I opted to manage H2 from a service. All my activities bind themselves to
this service in activity.onResume(), unbind themselves in onPause(). When
no activity have been bound to the service for 5 seconds, the service stop
itself, stop h2 and do some other cleanup.
So when my app goes in the
24 matches
Mail list logo
