On 30/08/13 00:41, Thomas Mueller wrote:
Hi,
> Is it practical with MVStore to use a single key with a list as the value containing the row id's
for a simple single column index?
Yes, unless the list of values doesn't fit in memory. Well, if the list of values is very big
(multiple KB) *and* changes a lot (many writes operations) then you probably shouldn't do that for
performance reasons, but it's possible.
But you could also use separate keys. If the key is large (many bytes) and the value is small,
then you should enable compression unless file size isn't an issue.
Regards,
Thomas
I might have done mapDB a disservice. It was failing with "Write thread failed" after a few hundred
lines, but i have just retried it and it worked OK.
Not sure why, but I need to investigate.
With reference to using ValueArray as key in non-unique situation, how are the required rows found,
for example if the ValueArray [0] is the searched for value and [1] contains the row? I have tried
to follow the MVSecondaryIndex code but the technique is not obvious (to me). It seems that a linear
search is used with an iterator on the key set.
regards
Paul
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
