Property, structural, and composite values
Cypher® provides first class support for a number of data value types. These fall into the following three categories: property, structural, and composite. This section will first provide a brief overview of each type, and then go into more detail about the property data type.
Property types
A property type value is one that can be stored as a node or relationship property.
The following data types are included in the property types category: Boolean
, Date
, DateTime
, Duration
, Float
, Integer
, List
, LocalTime
LocalDateTime
, Point
, String
, and Time
.
-
Property types can be returned from Cypher queries.
-
Property types can be used as parameters.
-
Property types can be stored as properties.
-
Property types can be constructed with Cypher literals.
Homogeneous lists of simple types can be stored as properties, although lists in general (see Composite types) cannot be stored as properties.
Cypher also provides pass-through support for byte arrays, which can be stored as property values. Byte arrays are supported for performance reasons, since using Cypher’s generic language type, List of Integer (where each Integer has a 64-bit representation), would be too costly. However, byte arrays are not considered a first class data type by Cypher, so they do not have a literal representation.
Structural types
The following data types are included in the structural types category: Node
, Relationship
, and Path
.
-
Structural types can be returned from Cypher queries.
-
Structural types cannot be used as parameters.
-
Structural types cannot be stored as properties.
-
Structural types cannot be constructed with Cypher literals.
The Node
data type includes: Id, Label(s), and a Map (of properties).
Note that labels are not values, but a form of pattern syntax.
The Relationship
data type includes: Id, Type, Map (of properties), start node Id, and end node Id.
The Path
data type is an alternating sequence of nodes and relationships.
Nodes, relationships, and paths are returned as a result of pattern matching. In Neo4j, all relationships have a direction. However, you can have the notion of undirected relationships at query time. |
Composite types
The following data types are included in the composite types category: List
and Map
.
-
Composite types can be returned from Cypher queries.
-
Composite types can be used as parameters.
-
Composite types cannot be stored as properties (with the exception of homogenous lists).
-
Composite types can be constructed with Cypher literals.
The List
data type can be either a homogenous collection of simple values, or a heterogeneous, ordered collection of values, each of which can have any property, structural or composite type.
The Map
data type is a heterogeneous, unordered collection of (Key, Value) pairs, where Key is a literal and Value can have any property, structural, or composite type.
Composite values can also contain null
.
For more details, see working with null.
Property type details
The below table provides more detailed information about the various property types that Cypher supports. Note that Cypher types are implemented using Java, and that below table references Java value constants.
Type | Min. value | Max. value | Precision |
---|---|---|---|
|
|
|
- |
|
|
|
Days |
|
|
|
Nanoseconds |
|
|
|
Nanoseconds |
|
|
|
64 bit |
|
|
|
64 bit |
|
|
|
Nanoseconds |
|
|
|
Nanoseconds |
|
Cartesian: ( Cartesian_3D: ( WGS_84: ( WGS_84_3D: ( |
Cartesian: ( Cartesian_3D: ( WGS_84: ( WGS_84_3D: ( |
The precision of each coordinate of the |
|
- |
- |
- |
|
|
|
Nanoseconds |
Float
, i.e. the closest value to zero. It is also possible to have a negative Float
.
Was this page helpful?