We discussed with Damien, David Strauss and Gerhard that splitting the translations table to the active and history table could make sense. Although is_active is indexed, so filtering on it should kick of irrelevant rows quickly, the data for history will grow very big. Currently the code does not anything with rows where is_active = 0, they are kept for history. The code could do something in the future however.

Comments

gábor hojtsy’s picture

Plans for is_active = 0 rows include stats on older contributions, blocking new suggestions which were submitted and rejected before, etc.

meba’s picture

So do we include non active rows in stats now? I am not sure...

gábor hojtsy’s picture

Title: Performance: split archived and live data » Split archived and live data
Component: Code » Performance
SebCorbin’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Issue summary: View changes

Bumping to 7.x