[application/connect] simplify connection logic ``application.connect`` now either sets a full featured ``DBAPISession`` to the ``WebRequest`` object or raises ``AuthenticationError``. The creation and usage of a fake DBAPISession is now handled by ``main_handle_request`` when needed. This means that fake DBAPISession are no longer tracked by the session manager and that user are not given anyway to retrieve them for a later request. This fake DBAPISession is still passed to ``core_handle`` because multiple cubes like registration or forgotten password need this behavior. We would like to get ride of it in the future. This clarification of the connection API greatly simplifies ``DBAPISession`` retrieval//creation process opening the way to improvements in this area. Related to #2503918

     1

for eschema in schema.entities():

     2

    if not (eschema.final or 'cw_source' in eschema.subjrels):

     3

        add_relation_definition(eschema.type, 'cw_source', 'CWSource', ask_confirm=False)

     4

     5

sql('INSERT INTO cw_source_relation(eid_from, eid_to) '

     6

    'SELECT e.eid,s.cw_eid FROM entities as e, cw_CWSource as s '

     7

    'WHERE s.cw_name=e.source AND NOT EXISTS(SELECT 1 FROM cw_source_relation WHERE eid_from=e.eid AND eid_to=s.cw_eid)')

     8

commit()