Short of debugging it itself, your best bet is to do dump before the
upgrade, and a restore to a fresh db after.
--
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
What's the status of this? We ran into the same issue when upgrading from
1.3.176 to 1.4.195
for our Android app. You can see more details here
: http://crashes.to/s/97b4cacc8ab.
Anything we can do to assist?
Regards
Carl
On Wednesday, October 26, 2016 at 4:39:36 PM UTC+2, Stuart Goldberg wrot
Please take a look at my post a number of months ago entitled "Timeout
trying to lock table". This is the same problem!
There is a bug somewhere. This issue continues to plague us intermittently.
On Monday, September 12, 2016 at 2:38:13 AM UTC-4, Dave Anonymous wrote:
>
>
> Sorry, but I'm not go
> Sorry, but I'm not going to find time to track this down.
> At a guess I would say it might have something to do with the Timestamp
> column
>
isnt it possible to debug this with my attached sql script to reproduce the
issue?
it is very important for us to know which tables could be affected
Sorry, but I'm not going to find time to track this down.
At a guess I would say it might have something to do with the Timestamp
column
--
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
@Noel
could you reproduce the issue?
--
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 t
