Search translations

The statement violates the constraint.

The statement violates the constraint, but the constraint is not mandatory.

The statement violates the constraint, but the constraint is just a suggestion.

The statement satisfies the constraint.

The constraint has not been checked because the statement is deprecated.

The subject entity of the statement is a known exception to the constraint.

Checks the constraint parameters of constraint statements.

These issues are problems with the constraint definition on the property, not with this statement.

The constraint is not implemented.

The constraint parameters are broken.

This constraint statement has some invalid parameters.

A <code>allowed_namespaces</code> constraint is assigned to the "[[Property:$1|$1]]" property and "$2" violates the namespace requirement, only the following "$3" namespaces are allowed.

Property "$1" only permits unique value annotations, ''$2'' already contains an assigned value. "$3" violates the uniqueness constraint.

Reset the notification status for the entire watchlist.

Flagged status of the revision.

changed the '''status''' of $1

Revoke the user's autoconfirmed status

view the current transcoding status

Check one particular constraint on the item Q2.

A <code>non_negative_integer</code> constraint is assigned to the "[[Property:$1|$1]]" property and the ''$2'' value annotation is violating the constraint requirement.

A <code>must_exists</code> constraint is assigned to the "[[Property:$1|$1]]" property and the ''$2'' value annotation is violating the constraint requirement.

A <code>single_value</code> constraint is assigned to the "[[Property:$1|$1]]" property and the "$2" value annotation is violating the constraint requirement.

Changes in the status of the progress of translations

Optional filter to return only the constraints that have the specified constraint ID.

The prepared statement $2 is not set up for the database ID $1.