The grouping date is a property representing the date when this grouping is
effective.
In erp5_accounting, when setting a grouping reference, the grouping date will
be set to the latest date of grouped line. When running reports with
"omit_grouping_reference", lines that are grouped after the end date of the
report will still be displayed.

SQLCatalog structure changed, and can be updated with:
alter table catalog add column grouping_date datetime after grouping_reference;

You might also want to set a grouping date on movements with a grouping
reference in the migration.

The editable field has to be registered in listbox editable fields to be used
as an url column.

Coordinate base class already inherit from Base, so no need for class
inheriting from Coordinate to inherit from Base again. Also, no need to reapeat
the property sheets that are already defined on Coordinate.

This use to work because categories are metanode and metanode were organisations

Prior to this change, such accessors were only generated if
'acquisition_base_category' was set on the accessor, but such accessor also
makes sense without acquisition_base_category.

Most coordinates from organisation were configured to acquire properties on the
region categories. This was not a problem, because prior to
36420d5c ("Fix class hierarchy for nodes"),
Categories were Organisations because they are MetaNode.

MetaNodes have always been Organisations, but this does not make sense at all.
This change reveal some hidden bugs with code that was working accidentally
because all meta nodes, such as categories use to be organisations and have all
the accessors from organisations

Although this also fixes "too many files" error, the way to upgrade some kinds
of objects should be reviewed in order to avoid such export/import.

This hurts performance with default catalog indexes.

to enable cache for anonymous, login should not be included in HTML itself based on the cookie value. it should be the browser's job.

New SQLBase._getMessageList method has a very simple ZSQLCatalog-like API,
and replaces SQL{Dict,Queue}_readMessageList DTML scripts.

'include_processing' parameter disappears (in favor of 'processing')
and default behaviour is to include messages being processed.

Also clean-up the comments.

test for now was passing thanks to a lucky good ordering in indexation

Revert both revert, as the original commits were just raising another bug but was not the cause of this bug

This reverts commit e89d10aa.
This reverts commit ff1ca703.

add work around for the performance regression introduced in Zope 2.12.23 in BTreeFolder2, for the case where we use BTreeFolder2 directly.

readd work around for the performance regression introduced in Zope 2.12.23 in HBTreeFolder2, for the case where we use HBTreeFolder2 directly.