Of course,it could also be that you've uncovered another tricky corner case - in which case we need some kind of
standalone test case to be able to debug it
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop
Hmmm, the root of the problem is that we need to know the types of columns when
creating a query plan.
I'm not aware of any standard SQL way of doing that.
If it's H2 specific, then using the CAST operator around the constant should
give us enough information.
On 2016/02/12 11:55 PM, 'David
I still get the following message using the latest version of the H2 jar
via maven:
[23505][23505] Unique index or primary key violation: "PRIMARY KEY ON
.PAGE_INDEX"; SQL statement:
I have a join table that seems to be the culprit - it uses a composite
primary key with foreign key
Hi Dmitry,
in regard to 2., I think that during the downtime of the primary server ,
the statements of the DB client were just going to only the secondary
server, and when the prim. was restarted, nobody was taking care of
synchronizing the prim. DB with the secondary DB to apply the changs
Hi.
We have a situation with a corrupt database causing NullPointerException on
select.
It's a very simple database with one table and one index. The database is
written using version 1.4.185, and cannot be read by that version or
1.4.191.
The database file was roughly 2.5 gb, but I deleted
