Hi,
I think the problem was Issue 566: MVStore: unique indexes that were
created later on did not work correctly if there were over 5000 rows in the
table.. This is fixed with version 1.4.179. But you will need to re-create
the database I'm afraid (via export to SQL script for example).
Regards,
Thanks Thomas.
the index was not used really in the app so we can live without it for now.
,, but good to know about the fix!
On Tuesday, 24 June 2014 07:09:16 UTC+1, Thomas Mueller wrote:
Hi,
I think the problem was Issue 566: MVStore: unique indexes that were
created later on did not
Hi,
I am using h2 version 1.4.178,
and get below error from the application which uses H2:
Row not found when trying to delete from index
PUBLIC.CONSTRAINT_2_INDEX_2: 12273; SQL statement:
*delete from XXX WHERE A = ? and B in ( NULL , 'a' ) and C=3*[90112-178]
when trying to run the