dae, stating the obvious doesn’t contribute anything to the thread. But thank you for your comment.
In the end, I deleted all the decks, and then rather than reimporting the collection without change (which already didn’t work), I reinstalled all the decks one by one instead, and it uploaded. There is another issue there, and looking at how much of a mess the deletion logic is, being largely without cascading deletes, I suspect that my usage created a lot of unreported, unremovable, orphaned data that was blocking the upload, or that the database was building inconsistently. That’s my hypothesis.
@dae was probably in a bit in a hurry there, with the 2.1.50 Beta and lots of development tasks to do. Looking at how many support queries he answers each day, I think we can forgive him that oversight
Until Damien gets back to this, linking to some code examples of that messy deletion logic would help. If you got suggestions how to improve it, you can also open an issue or PR on GitHub.
I’m new to this sorry. Thanks.
Regarding the deletion logic being without cascading deletes, I’m referring to all the manual steps needed (delete media, delete trash, rebuild database, manually clear down orphaned Note types), and with that being the case, and seeing the behaviour I’ve experienced re: the dataset size remaining unchanged for me even after deleting the decks that pushed it over the limit. This is a user report, not a developer report, hence the use of the word hypothesis
Actually, now that I think about it, I was also getting another (completely false) warning message, on deleting a deck and then trying to re-import it, claiming that I had exceeded the card limit of >1,000,000 cards, which was completely false, and the import succeeded anyway…
As is stated in the link @dae has sent, media has nothing to do with it. A common cause for this error are notes with lots of websites copied into them.
“4. Delete decks” is a bit vague. Did you delete all of your decks? It might well be that a single deck is responsible for almost all of the 485MB, and the other decks only have a few KB each.
These are all very different routines and not usually used simultaneously, so it wouldn’t make sense to bundle them.
Delete media moves media to the trash bin, Delete trash empties the bin. This is an extremely widespread and user-friendly design pattern.
Check database can resolve some errors with decks, cards, notes, etc. It doesn’t handle media.
Orphaned notetypes have to be removed manually, because more often than not, the user wants to keep them for future use. Also, since you need a notetype to create notes, they need to to exist beforehand.
It was incorrectly reporting that I had over 1M cards, and that the data exceeded 485mb even after decks were deleted (LIFO) and database “checked”. Something is up.
Delete-of-media-wise, I still think cascading delete of deck associated data, is a clean and obvious win (associated Notes could be checkbox optional).
Anyway, not an issue for me now.