Bring back the separate web-side entity cache Prior to changeset 635cfac73d28 "[repoapi] fold ClientConnection into Connection", we had two entity caches: one on the client/dbapi/web side, and one on the server/repo side. This is a waste, but it is actually needed as long as we have the magic _cw attribute on entities which must sometimes be a request and sometimes a cnx. Removing the duplication caused weird problems with entity._cw alternating between both types of objects, which is unexpected by both the repo and the web sides. We add an entity cache on ConnectionCubicWebRequestBase, separate from the Connection's, and bring back the _cw_update_attr_cache/dont-cache-attrs mechanism, to let the server/edition code let caches know which attributes have been modified Entity.as_rset can be cached again, as ResultSet no longer modifies the entity when fetching it from a cache. Contrary to the pre-3.21 code, _cw_update_attr_cache now handles web requests and connections in the same way (otherwise the cache ends up with wrong values if a hook modifies attributes), but dont-cache-attrs is never set for (inlined) relations. Closes #6863543

     1

# -*- coding: utf-8 -*-

     2

# copyright %(year)s %(author)s, all rights reserved.

     3

# contact %(author-web-site)s -- mailto:%(author-email)s

     4

#

     5

%(long-license)s

     6

"""%(distname)s precreate script, executed at instance creation time or when

     7

the cube is added to an existing instance, before the schema is serialized.

     8

     9

This is typically to create groups referenced by the cube'schema.

    10

"""