Increment replies_count (MastoAPI)

Closes #756 (closed)

added 1 commit

• e3a824dd - Increment replies_count on replies (MastoAPI)

Compare with previous version

added 1 commit

• 570260dc - Increment replies_count on replies (MastoAPI)

Compare with previous version

added 1 commit

• a39b840f - Increment replies_count on replies (MastoAPI)

Compare with previous version

added 1 commit

• b832268f - Increment replies_count on replies (MastoAPI)

Compare with previous version

added 1 commit

• b24ab71f - Increment replies_count on replies (MastoAPI)

Compare with previous version

added 1 commit

• 568e3485 - Increment replies_count on replies (MastoAPI)

Compare with previous version

unmarked as a Work In Progress

mentioned in commit 21ff78cd

merged

mentioned in issue #769 (moved)

mentioned in issue pleroma-fe#466 (closed)

This migration is actually O(n^2), I think, which makes it unreasonable for large instances.

I suggest some kind of lazy filling of this value if it isn't present is required. Most old posts will never be touched so it will reduce the load as well as spreading it over a longer timeperiod.

Well, it doesn’t seems to be much of a blocker if the replies_count is wrongfully 0, the issue filled by @lambadalambda looks more like a filler one.

Dang, my bad

mentioned in issue #387 (closed)