GitLab

it causes flake8 error on some of its versions.

We don't want to force using 'identity' in this case which may be easily
handled by detecting variable is a `ColumnAlias` and relation is 'eid'.

Closes #15393583

closes #15613724

related to #15613724

This refactoring will ease later implementation of
i18n cube customization.

related to #15613724

Path can actually be accessed from `req` object. This allows to avoid duplicating
this information.

This cset prepares the next ones that aim at adding the language as a prefix of the
relative path.

--HG--
branch : 3.23

--HG--
branch : 3.23

--HG--
branch : 3.23

Binary isn't hashable hence can't be added to a set. Test added.

--HG--
branch : 3.23

--HG--
branch : 3.23

Reformat "context" dict to have it PEP8 compliant along the way (only white
space changes).

In unittest_utils.py, use unittest2's TestCase instead of lgc.testlib one to
benefit from subTest API.

Closes #15409885.

So to as to make it clear that changelog needs to be edited
before the Debian package may be published.

An error in the jquery selector of the html widget controlling the log
level was the cause of this bug.

Closes #15772634

So that, in particular, its ccplugin.py does not get loaded (which would hide
the "pyramid" command in cubicweb).

Related to #14023058.

Related to #14023058.

This does a partial "drop_cube('pyramid')" equivalent but only considering
CWProperty. We cannot just drop the cube since we have introduced some
mechanism to exclude pyramid cube from config's cubes list and that would make
MigrationHelper.cmd_drop_cube() call not return "pyramid" cube.

Related to #14023058.

Drop unused stuff.

This is not a desired part of the store API. Mapping between extid and eid
should be done by the importer.

This had been backported from the dataio cube, but not one seems to rely on it
yet, so don't provide any backward compat.

PGHelper has no logger, the store has.

Closes #13436818

It was crashing on attempt to remove an unexisting constraint. This code may be
removed safely as it's expected to be handled by the constraint removal hook.

Notice that adding a vocabulary on shortpara makes yams change the varchar max
size. This is arguable but not the point of this test, so simply adapt the max
size defined in the schema coherently so we don't have to bother with that at
this point.

Grafted from f87da59faea1 in default branch.

--HG--
branch : 3.23

Some fixes there are necessary for client work depending on cubicweb 3.23.

--HG--
branch : 3.23

Closes #14789440.

--HG--
branch : 3.23

And thus consider `_forced_mode` first.
Related to #14789440.

--HG--
branch : 3.23

--HG--
branch : 3.22

--HG--
branch : 3.22

--HG--
branch : 3.22

Query the information schema to retrieve existing constraint (primary key and
unique) and drop them.

Thus don't use anymore DROP CONSTRAINT IF EXISTS (not implemented by e.g. old
versions of sqlserver). To do so a missing DISTINCT was necessary to avoid
duplicates.

--HG--
branch : 3.23