Sorry, the exception only happens when closing a connection with a large
amount (114508) of MERGE queries executed, and I couldn't post the test
case for you.
The table only contains three columns as "name VARCHAR PRIMARY KEY, df INT,
category_counts VARCHAR"
This is reproducible in both 1.4.183 an
Hi,
there has to be some other problem. Now I see - I intended to update the
table, so not providing default columns was not an issue. But somehow the
original data in the database changed and some of the rows that I wanted to
update were deleted. So now the merge tried inserting those rows and
Hi Thomas,
The database file size in 1.4.184 is much, much better than in earlier
1.4.x releases.
I've done some trials and these are my findings:
1.3.176: Fully loaded database after shutdown is 317 Mb
1.4.184: Fully loaded database after shutdown is 380 Mb
This seems reasonable.
On Friday,
