The issue seems to be fixed.
Thanks,
On Tuesday, December 19, 2017 at 1:45:43 AM UTC-8, Noel Grandin wrote:
>
> ah, ok.
>
> I have pushed an attempted fix to master, please try it out if you are
> able to.
>
>
--
You received this message because you are subscribed to the Google Groups "H2
Hi,
I need an array of Longs using MVStore and the only solution I can find is
to use MVMap with the key as the Long and a dummy value.
Is this the best approach or is there a better way?
If an MVMap is used, what data type would be preferred for the dummy value
as null is not allowed?
Paul Fra
Hey there,
I've been playing with H2 1.4.195, trying to get an ordered resultsset from
a query that contains a join.
In the plain vanilla case, H2 tends to create a resultset containing
everything from the join plus the sort columns and then sort the set in
memory. Here's an example for what I
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
> On 21 Dec 2017, at 8:29 pm, Noel Grandin wrote:
>
> On 2017/12/21 11:42 AM, Matthew Phillips wrote:
>> The serializer would need therefore to potentially access the H2 MVStore
>> while reading an object, calling back 'up' the stack as it were to read
>> parent object(s). This strikes me as a
try using more aggressive trace options:
http://h2database.com/html/features.html#trace_options
--
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+unsub
On 2017/12/21 11:42 AM, Matthew Phillips wrote:
The serializer would need therefore to potentially access the H2 MVStore while reading an object, calling back 'up' the
stack as it were to read parent object(s). This strikes me as an unexpected thing to do, and I wonder if H2 would have a
pro
I want to use H2's MVStore with a large number of objects (maps), many of
which are derived from each other, often differing in a single property.
I'd like to write a plugin serializer that can write an object as a
reference to another object plus a delta from that object. This would
reduce sto
