GitLab

If the context manager is exited via an exception, the original
permissions should be restored.

SQLServer refuses to index an unlimited text column, so we should drop
unique_together constraints (which imply an index) before we drop size
constraints.  Closes #5560601.

Until now we would:

- remove the old size constraint from the in-memory schema
- call update_rdef_column which removes the size restriction from the
  column's type
- add the new constraint object
- call update_rdef_column which adds the size restriction back

This breaks on SQL Server when the column is involved in an index (e.g.
as part of a multi-column unique constraint), because in the
intermediate stage the column's type is "nvarchar(max)", which is not
indexable.

Of course we must still detect the case where a size constraint is
really dropped and update the db schema accordingly.

Closes #5557633.

On entity creation, if there are some local permissions on the relation,
we have no way of checking them since neither the subject nor the object
of the relation exists yet. In such a case, we should add the link by
default, for consistency (see other places where we use
`may_have_permission`).

Closes #6711900

Prevents the "modify" action from being shown when there is nothing to
edit.

When selecting an inlined creation form, we should catch the
NoSelectable exception that will be raised if the user cannot add
entities of the target type (this is not and cannot be verified earlier)
or if some other custom selector prevents the form from being selected.

Closes #6510921

Otherwise a simple sync_schema(syncprops=False) turns the subsequent
sync_schema() calls into a no-op.

Closes #6510918.

Without the fix in migractions.py, the introduced test crashes with an
operational error because of an attempt to write to a non-existing
relation table (computed relations are not materialized).

Closes #6304946

as this method may be used from outsite the class (eg in UpdateFTIHook), this is
the proper way to consider it anyway.

Closes #6206636

We were assuming that if an entity is in the connection's cache, it has
a cw_edited attribute.  This doesn't seem to always be the case.  At
least in cubicweb 3.21, merging the web and repo-side caches makes this
more likely, but Denis says he's also seen this on 3.20.

[web/views/formrenderer] remove `cubicweb:target` attribute on form once the target <iframe> is inserted

For some unknown reason, IE9 does not want to submit the form inside
the <iframe> when the ``cubicweb:target`` attribute exists.

(closes #5377672)

[forms] don't display 'remove' link of inlined form for the first entity related using a '+' cardinality to its parent entity

Closes #5227394

Its presence in globals is deprecated and going away.

Because css_class attribute may be overriden by bootstrap after button creation and this
modification has to be taken into account.

closes #5457548

Added tag cubicweb-version-3.19.11, cubicweb-debian-version-3.19.11-1, cubicweb-centos-version-3.19.11-1 for changeset 1ae64186af94

Also fix a bug in the backwards-compat eid_type_source method where it
returned an extid (possibly null) instead of a source name.

With these changes, migrating a database from cw 3.12 is now possible.

Closes #4962681

Closes #4965410

Recent versions of pyodbc return bytearray objects for binary data.

When given a Yams snippet of the form `<etype> <rtype>` ``xy.xeq()`` will
return the XML snippet equivalent to this relation in the form of a tuple
`(subject, rtype, object)` so ``item`` will always be a tuple here.

In fact, the correct code appears just a few lines above (around line 88) for
final relations so I guess this is a copy-paste mistake.

Closes #4745929.