[repoapi] fold ClientConnection into Connection Connection replaces ClientConnection everywhere. Some notes: * testlib: .client_cnx and .repo_cnx become aliases of .cnx (we might not want to tell people to update their tests again for just no real benefit, so we'll live with these aliases for a while) * entity.as_rset must not be cached because we risk caching result sets having a Connection object as .req (helps unittest_breadcrumbs) * entity._cw_dont_cache_attributes loses its repo/request special paths and only keeps its storage/bfss user (this helps unittest_wfobjs) * moreover, entity.cw_instantiate and .cw_set stop overriding the attributes cache *after* the before_*_entity hooks have run, because there is no need to (it is now actually harmful to do it and unittest_hooks.test_html_tidy* tests remain green because of this) * rset._build_entity sticks its .req onto the entity just fetched from the cache, because otherwise it might carry a _cw that is a Connection object where a Request is expected (helps unittest_views_actions) * we get overall better cache usages (entity caches were split over Request + ClientConnection and Connection), hence the changes unittest_entity and unittest_wfobjs * void the ecache when providing the cnx to a request object Having the entity cache pre-filled when we bind it to the request object hurts because these entities are bound to Connection objects, that lack e.g. `.form` or `.add_js` and crash the views subsystem. Thus, the unittest_testlib.test_error_raised test will are kept green. Closes #3837233

     1

About this site

     2

===============

     3

     4

This web application is based on the CubicWeb knowledge management system

     5

from Logilab_. CubicWeb is made of an object database and a web

     6

framework. It allows to develop an application by defining a set of

     7

entities and their relationships, plus a set of views that present the

     8

data selected from the object database using a specific query language.

     9

    10

This application has a precise schema_ and can be considered an

    11

example of a semantic web database, as it can export the data to XML

    12

and others formats and is not limited to publishing HTML.

    13

    14

Supported formats: |microformats|_ - JSON_ - |rss|_ - |dublincore|_

    15

    16

.. |microformats| image:: /data/microformats-button.png

    17

.. _microformats: http://microformats.org

    18

.. _JSON: http://www.json.org/

    19

.. |rss| image:: /data/rss-button.png

    20

.. _rss: http://www.rssboard.org

    21

.. |dublincore| image:: /data/dublincore-button.png

    22

.. _dublincore: http://dublincore.org

    23

    24

.. _Logilab: http://www.logilab.fr/

    25

.. _schema: ../schema