ActivePeriodMixin use on General Ledger reports result in a huge performance penalty
Because of the structure of the active
field search (which basically makes an id IN SELECT id FROM general_ledger WHERE some_date_conditions
) it results in an almost doubling of the time spent to execute the query.
We should probably reimplement search_active
for the models inheriting from GeneralLedger.