Lada's comment regarding "config false" pagination

[kwatsen]

Lada writes:

The handling of "config false" lists brings about considerable complexity.
Also, it seems to cater for SQL database backends and I am not sure whether the
constraints on "config false" data can also be easily implemented with other
backend architectures that might be suitable for huge datasets, such as Xapian
or ElasticSearch. What I am missing here is a description of typical use cases
for "config false" data and a cost/benefit analysis. Perhaps it could make
sense to adopt a simpler and less flexible approach for "config false" data.

[kwatsen]

Add yto Section 2 that it:

• tries to cater to LCD (least common denominator) database
• there might be several DBs (as a unified datastore) - a federated database