GitLab

--HG--
branch : 3.20

--HG--
branch : 3.20

--HG--
branch : 3.20

ensure i allways exists whatever f content is

--HG--
branch : 3.20

--HG--
branch : 3.20

--HG--
branch : 3.20

accessing self._cw.message now(?) eat the message, so don't call
"self._cw.message" twice.

Otherwise the notification emails sent via an internal_session never honor the
EMAIL.sender-name configuration option.

'Connection' object has no attribute 'HOOKS_DENY_ALL'

When migrating from a pre-3.10 database, the CWSource entity type and
cw_source relation type are not known, but authenticate should still
work to be able to add them.

Closes #9720390.

This isn't French.

unittest_views_basecontrollers.py's
EditControllerTC.test_edit_mandatory_inlined3_object regressed with
changeset dcbb64d3a1d9 because it relied on POSTing nonexisting eids.
This seems like a silly idea, but let's keep the behaviour unchanged.

Getting an unexpected test error though:
ERROR: test_edit_mandatory_inlined3_object (unittest_views_basecontrollers.EditControllerTC)

When CWProperty instances are touched, the corresponding value gets
updated in vreg['propertyvalues'], but their type was ignored.

This implies handling the reparenting case sooner, otherwise the
child entity modifications are cancelled (see 113e9da47afc).

Add a new test to ensure non-regression in all previous tests.

Closes #10291977.

If we can't build a suitable COPY command (e.g. because data has
unsupported type), use executemany instead. Regression introduced in
3.20.0.

The entity included in the composite will be deleted in such a case, so
the field is not required even when the cardinality is '1' or '+'.

Related to #8529868

Otherwise we fill up the tempdir.  Closes #9133268.

Composite relation removal via the EditController trigger an entity
removal. Changes on such a to-be-removed entity must be cancelled as
they may trigger integrity errors before the deletion occurs.

Closes #8529868.

In CubicWeb 3.18 the semantics of dropping a composite relation were changed.
It had before the effect of deleting the subentities.

Now the edit controller must handle this by itself (it was not adapted then by
mistake).

So if it detects the removal of a composite relation (on the browser side, the
user clicked on the "remove" action), the subentity is now explicitly deleted.

It was chosen not to change the form generation but the EditController:

- to ensure pre-3.18 forms backward compat
- to avoid the introduction of a specific entity-deletion API (RQL is probably
  our best API for complex DB operations)

Related to #8529868.

* `entity` defined at method entry
* a combined `continue` and a dedent of the next big block
* some vertical white space

Related to #8529868.

[sources/native] ask permission to continue restoring even if metadata do not match (closes #7771864)

Moreover we try to clarify the message (Expected/Found was never too clear for users).