Search translations

A <code>unique_value_constraint</code> constraint is assigend to the the "[[Property:$1|$1]]" property hereby only permits unique value annotations, ''$2'' already contains an annotated value with "$3" violating the uniqueness constraint for the current subject.

A <code>unique_value_constraint</code> constraint is assigend to the the "[[Property:$1|$1]]" property which only permits unique value assignments and the ''$2'' value annotation was already found to be annotated in the "$3" subject.

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

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

The constraint is not implemented.

Checks the constraint parameters of constraint statements.

The property <code>$1</code> is not set.

The statement satisfies the constraint.

The statement violates the constraint.

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

The constraint parameters are broken.

Adds the value of the page property.

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

Unexpected conflict between the Property type "$2" and the value type "$1".

<code>$1</code> is not a supported value of the <code>$2</code>. The possible values are: $3.

go to constraint

The constraint is not checked on this kind of snak (main snak, qualifier or reference), so the constraint check is skipped.

The value for the parameter "$1" must be a property, not "$2".

The allowed {{PLURAL:$1|value for this property is|values for this property are}}:

The value to check for the previous property or field

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

The value type for this data type is <code>$1</code>.

Check constraint parameters of all constraints on a property.

Value <code>$1</code> not in enum for property $2