HI
Since we now require Java1.5, perhaps we should be using
java.util.concurrent.locks.ReentrantLock(true/*fair*/)
(note the use of the fairness parameter.)
instead of using the synchronized keyword?
I suspect it would reduce the incidence of "Timeout trying to lock
table" when
On 2013-02-27 01:14, Ashwin Jayaprakash wrote:
*Issue 1: *This seems alright except for the deepest join on c where
the predicate (c.type = 'answers') _does not get pushed down_ in the
TableFilter.getFilterCondition() for "c" where it is null.
Patches are welcome.
--
You received this mess
I have something to add to my previous request. For a moderately complex
query like this:
select *a*.id, *a*.age, b.id, *c*.id, *c***.type
from *a*
left outer join *b* on a.id = b.id
left outer join *c* on b.id = c.id
where *a*.age < 42 and *c*.type = 'answers'
Here, a.id, b.id, c.id are a
Thanks Steve. That works.
On Thursday, 14 February 2013 22:51:04 UTC-8, Steve McLeod wrote:
>
> As follows:
>
> create cached temp table if not exists foobar ;
>
> select count(*) from information_schema.tables
> where
> table_schema = 'PUBLIC'
> and table_type = 'TABLE'
> and storage_ty
Hi Noel,
I had posted this on one more
forum:
http://h2-database.66688.n3.nabble.com/MVCC-and-SELECT-FOR-UPDATE-td2140527.html
Thats because i thought this & the other one isn't related. And it was
supposed to be a question for the person who had replied to that post.
Sorry for that. Will delet
I have a table like this:
CREATE TABLE t (a INT NOT NULL, b INT NOT NULL, PRIMARY KEY(a, b))
This implicitly creates an index:
CREATE INDEX t(a, b)
To improve the efficiency of some queries, I have also created an index:
CREATE INDEX t(b)
Is it worth also creating an non-composite index on
Please don't post the same question twice, it just annoys the people
here and makes us less likely to help you.
On 2013-02-26 15:37, srinivas upadhya wrote:
Hi,
We are getting this exception on trying to insert to a table:
--
You received this message because you are subscribed to the Googl
Hi,
We are getting this exception on trying to insert to a table:
insert into materials (id, a, b, c, d, e, f) values (null, ?, ?, ?, ?, ?,
'a') [50200-168]; nested exception is org.h2.jdbc.JdbcSQLException: Timeout
trying to lock table ; SQL statement:
insert into materials (id, a, b, c, d, e,
OK - Thank you Noel!
From: Noel Grandin
Sent: Tuesday, February 26, 2013 11:11 AM
To: Riccard Montén ; h2-database@googlegroups.com
Subject: Re: Physical disconnection caused h2 to grow as big as possible
Yes, it is normally handled by the transaction log.
Normally, what happens is that all
Yes, it is normally handled by the transaction log.
Normally, what happens is that all of the data does not get to the disk.
In which case we use our transaction/undo log to undo all in-progress
modifications.
However, in your case it looks like the actual header of the DB was
corrupted, and t
Yeah, at this point you're probably better off asking on the Eclipselink
mailing list.
Weird, I would have thought H2 would be well supported because Eclipse
uses it internally.
On 2013-02-26 11:35, Dries wrote:
Because, once I enable my sessionCustomizer class, eclipselink no
longer uses
Because, once I enable my sessionCustomizer class, eclipselink no longer
uses the correct statement (CALL NEXT VALUE FOR), but instead uses :
[EL Fine]: 2013-02-22
14:50:01.291--ClientSession(2052114141)--Connection(1340006540)--Thread(Thread[main,5,main])--UPDATE
SEQUENCE SET SEQ_COUNT = SEQ
I don't use Schema Generation by eclipselink, the tables are created in h2
directly. That I think is the reason h2 isn't able to link the sequence
name to the auto_increment field.
On Tuesday, February 26, 2013 7:31:19 AM UTC+1, Christoph Läubrich wrote:
>
> Do you use annotations? Schema gener
On 2013-02-22 15:55, Dries wrote:
I'm able to make that statement work on the correct tables and fields
in h2, but h2 doesn't allow changes to meta tables, so that doesn't
solve the problem either.
login.getPlatform().setSequenceCounterFieldName("CURRENT_VALUE");
login.getPlatform().setSequenc
I'm sorry, but your H2 database was corrupted beyond the abilities of
the Recover tool to deal with.
On 2013-02-22 23:45, PetitPo wrote:
I´ve been using h2 as db with OOBase as GUI for some years.
With some SQL-knowledge I can handle what I need mostly. I´m not an
experienced programmer and I
Need the entire exception please, this is just part of it.
On 2013-02-22 20:19, Cesar Rodriguez wrote:
Hi,
After de Recovery, still have the
"java.lang.ArrayIndexOutOfBoundsException" error:
Query:
SELECT * FROM PACIENTE ORDER BY ID_PACIENTE DESC;
Response:
General error: "java.lang.Array
16 matches
Mail list logo
