I opened the .db file in SQLite Manager and deleted the entire contents of
the "log" table. I no longer have the past statistics, but at least the .db
file is small again. Problem solved.
On Thursday, March 30, 2017 at 6:50:34 AM UTC+3, Pete Kovalenko wrote:
>
> My problem: after importing "Mnemosyne 2.x *.db files" only active cards
> of the source .db are imported (which is nice), nevertheless the
> destination .db bloats enormously, as if the entire source .db was imported.
>
> I merged my own .db and my daughter's .db into one file so we now do our
> repetitions together, which is fun. But I kept adding new cards to my old
> .db in order to get them a little more mature, to correct mistakes, to add
> sounds/pictures/videos etc before transferring them to our main .db file. I
> was adding ≈200 new cards a week. Did it weekly for 3 or 4 weeks and
> noticed that Mnemosyne became real slow for some reason. Checked the .db
> file, and it was huge -- 133 Mb. "Compact Database" command didn't do much.
> For the sake of experiment I left only 2 cards active (out of more than
> 19000) and imported this huge .db into my old personal .db -- and now its
> size is 137 Mb (with only 55 cards in it). What should I do? ("Compact
> Database" command doesn't do much to the size of these files.) (my
> Mnemosyne version is 2.3.5)
>
--
You received this message because you are subscribed to the Google Groups
"mnemosyne-proj-users" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/mnemosyne-proj-users/487c88d0-cd27-4c44-befb-5cfd98519754%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
