intermine.constraints.ConstraintFactory:
A constraint factory is responsible for finding an appropriate
constraint class for the given arguments and instantiating the
constraint.
intermine.model.Reference:
In addition the the behaviour and properties of Field, references
may also have a reverse reference, if the other record points back
to this one as well.
intermine.constraints.LogicNode:
Objects which can be represented as nodes in the AST of a
constraint logic graph should inherit from this class, which
defines methods for overloading built-in operations.
intermine.constraints.CodedConstraint:
Constraints that have codes are the principal logical filters on
queries, and need to be refered to individually (hence the codes).
intermine.constraints.BinaryConstraint:
These constraints assert a relationship between the value
represented by the path (it must be a representation of a value, ie
an Attribute) and another value - ie.
intermine.constraints.TernaryConstraint:
These constraints request a wide-ranging search for matching fields
over all aspects of an object, including up to coercion from
related classes.
intermine.constraints.ListConstraint:
These constraints assert a membership relationship between the
object represented by the path (it must always be an object, ie.
intermine.webservice.DictValueParser:
Parses jsonrow formatted rows into dictionaries where the key is
the view string for the cell, and the value is the contents of the
returned cell.
intermine.webservice.ResultObjParser:
Parses jsonrow formatted rows into ResultRows, which supports key
access by list indices (based on the selected view) as well as
lookup by view name (based on the selected view value).
intermine.webservice.ResultRowParser:
Parses jsonrow formatted rows into ResultRows, which supports key
access by list indices (based on the selected view) as well as
lookup by view name (based on the selected view value).
intermine.constraints.Constraint:
All constraints inherit from this class, which simply defines the
type of element for the purposes of serialisation.
intermine.constraints.CodedConstraint:
Constraints that have codes are the principal logical filters on
queries, and need to be refered to individually (hence the codes).
intermine.constraints.BinaryConstraint:
These constraints assert a relationship between the value
represented by the path (it must be a representation of a value, ie
an Attribute) and another value - ie.
intermine.constraints.TernaryConstraint:
These constraints request a wide-ranging search for matching fields
over all aspects of an object, including up to coercion from
related classes.
intermine.constraints.ListConstraint:
These constraints assert a membership relationship between the
object represented by the path (it must always be an object, ie.
intermine.constraints.SubClassConstraint:
If an object has a reference X to another object of type A, and
type B extends type A, then any object of type B may be the value
of the reference X.
intermine.webservice.ResultObject:
An object used to represent result records as returned in jsonobjects format
============================================================================
intermine.constraints.TemplateConstraint:
Constraints on templates can also be designated as "on",
"off" or "locked", which refers to whether they
are active or not.