Diagnostic codes

This atom is created but not used in any rule or query. Consider removing it if it’s not needed.

This symbol is not expected in this context. Check the syntax of the rule or query.

The parser reached the end of the file while expecting more input. Check for missing symbols or incomplete rules.

This symbol is not expected in this context. Check the syntax of the rule or query.

The parser expected a different symbol or token. Check the syntax of the rule or query.

This symbol is not recognized by the parser. Check for typos or unsupported syntax.

This symbol is not recognized by the parser. Check for typos or unsupported syntax.

The parser expected a specific symbol at the end of the file. Check for missing symbols or incomplete rules.

The parser expected a specific symbol before the current position. Check for missing symbols or incomplete rules.

The parser encountered an unexpected symbol while expecting another one. Check for typos or unsupported syntax.

An unknown error occurred during parsing. This may be due to a bug in the parser or an unsupported syntax.

This atom is used in a rule or query but has not been declared. Declare the atom to use it, either as a fact (a rule with no head and only constants, like person("First Name", "Last Name", 37).) or by importing it with @input.

This atom is used in the head of a rule and as an input. This may cause confusion or unintended behavior. Consider creating a new atom instead.

This atom is already declared as an output. You cannot declare it again. Remove the duplicate declaration.

This atom is used as an output but has not been declared as such. Check the spelling of atom name or declare it the head of a rule to output it.

This error occurs because the Vadalog program violates the wardedness property, which is a key safety condition in Warded Datalog±.

This @input atom has no bindings. You need to add @bind and @mapping rules to bind the input atom to a data source. To fix it, add a @bind rule to bind the input atom to a data source, and a @mapping rule to map the columns of the data source to the terms of the input atom. Example: @input("atom"). @bind("atomName", "data source", "outermost container", "innermost container"). @mapping("atomName", column1positionInAtom, "column1Name", "column1Type"). @mapping("atomName", column2positionInAtom, "column2Name", "column2Type").

This @output atom has no bindings. The output will be sent with the response, but you may want to add bindings to control the output.

This error arises because the program violates the safe taintedness condition for Equality-Generating Dependencies (EGDs).

This hint indicates that the head of the rule contains an equality-generating dependency (EGD) that can lead to existential variables being made equal during reasoning.

The annotation requires at least one term.

Variables used in conditions must be bound in a positive atom or in an assignment.

If a variable occurs in the head of a rule and is also used in a negated body atom, it must have a binding in a non-negated body atom. For example, if 'X' is in the head and 'not p(X)' is in the body, there must be another atom like 'p(X)' in the body.

The number of arguments in the annotation must match the expected number. For example, if the annotation is '@mapping', it should have the correct number of arguments as defined in the specification.

In Vadalog, if a variable is not used in the head of a rule, it should be replaced with an underscore ('') to indicate that it is anonymous. For example, instead of using 'X' in the head, use '' if 'X' is not used.

The number of terms in the atom’s signature must match the number of terms in the atom. For example, if the atom is 'p(X,Y)', then the signature must have 2 terms, not 3. If the missing variable need not to be brought to the head, you can use the anonymous variable _ to mark them.

The mapping position must be an index (0-based) that indicates the position of the term in the atom’s signature. For example, if the atom is 'p(X,Y)', then the mapping position can be 0 or 1, but not 2.

Non-Afrati linear join. A linear program is a Datalog program such that every clause in the program has at most one intensional atom in its body.

In Datalog, existential variables are not allowed. They can only be used in Vadalog rules. If you need to use an existential variable, consider using other fragments instead.

The atom is not in a Guarded rule, which is a rule that has a guard. A guard is an atom that contains all the universally quantified variables of the rule.

The atom is not in a Frontier Guarded rule, which is a rule that has a frontier guard. A frontier guard is an atom that contains all the universally quantified variables of the rule head.

The rule contains more than one atom in the body, which is not allowed in linear Datalog programs.

Rule is not Weakly Guarded but because it misses a weak guard atom. A weak guard is an atom that contains all the dangerous universally quantified variables.

Rule is not Weakly Frontier Guarded but because it misses a weak guard atom. A weak guard is an atom that contains all the dangerous universally quantified variables.

In Vadalog, each atom can have at most one binding. Remove one.

In Vadalog, extensional atoms cannot be used as outputs. If you want to output extensional data, create a copy rule that transforms the extensional atom into an intensional one.

In Vadalog, facts cannot contain variables. Replace variables with constants.