# Compatibility and limitations

[Wiki](../README.md) / [Reference](README.md)

**On this page**

- [Query language](#query-language)
- [Values and indexes](#values-and-indexes)
- [Graph data science and APOC](#graph-data-science-and-apoc)
- [Transactions and scale](#transactions-and-scale)
- [Protocol and administration](#protocol-and-administration)

Use this guide to check your application's queries and driver compatibility
when evaluating a Galactus DB release.

## Query language

Supported: read/write patterns, optional matches, MERGE, list/pattern
comprehensions, CASE, reduce, FOREACH, map projection, XOR, inline WHERE,
aggregates including DISTINCT, EXISTS/COUNT/COLLECT subqueries, quantified path
patterns, `=~`, LOAD CSV, CALL/YIELD and CALL IN TRANSACTIONS with ON ERROR
policies. See [Cypher](../cypher/README.md).

`=~` and the regex APOC functions match in linear time, so backreferences,
lookaround, atomic groups and possessive quantifiers are rejected. A quantified
path pattern cannot be nested or contain a variable-length relationship.
`n CONCURRENT` batches are accepted but run one after another. Strings use
functions such as `substring`; list subscript/slice syntax does not apply to
strings, as in Neo4j. `PROFILE` executes queries, including writes, and reports
per-operator counters; [EXPLAIN](../cypher/planning.md) does not execute them.

## Values and indexes

Exact `DECIMAL` values of up to 38 digits are supported from version 1.7.2, and
Bolt carries them as strings with their exact digits; see
[decimal numbers](../types/decimal.md). All six temporal types and named IANA
DateTime zones are supported; the vendored
zone table covers 1900–2100. Time-of-day zones remain offset-only.
See [temporal edge cases](../types/temporal.md), including duration aliases and
ignored truncation overrides. Geometry and geography now support all seven linear
shape families, strict WKT/WKB/GeoJSON, predicates, overlays and centroid alongside
legacy points. Computations require XY; geographic overlays generally need a
common open hemisphere. Polar GeoJSON export, ellipsoidal operations and coordinate
reprojection are unsupported. See [spatial shapes](../types/spatial-shapes.md).

Hash, range, composite, element, vector, point, spatial shape, full-text and
[relationship property](../indexes/relationship.md) indexes are implemented.
Constraints cover ordinary/group/element uniqueness, existence, node keys and
[property types](../indexes/constraints.md#property-type-constraints). A
relationship index covers one property of one type and is used when that
relationship is first or last in the pattern. A database using either cannot be
opened by version 1.0.1. Composite relationship indexes are
absent. HNSW is approximate: exact rescoring orders only the candidates found,
and cannot guarantee full-search recall. Full-text is BM25 bag-of-words with
OR semantics; no phrase, fuzzy, stemming, boolean-query or highlighting support.
See [index selection](../indexes/README.md).

Shape indexes require an explicit `db.index.spatial.intersects` call; spatial
WHERE clauses do not automatically select them. Cartesian envelopes prune
candidates; geographic indexes currently refine a scan. Drivers receive a
versioned map envelope for spatial shapes and can import it with `spatial.fromMap`.

## Graph data science and APOC

Native database-scoped projections support centrality, similarity/KNN, FastRP,
community algorithms including Label Propagation and Leiden, and pathfinding,
including Galactus's own Hourglass shortest-path algorithm
(`gdb.shortestPath.hourglass`, not part of Neo4j GDS), and Galactus's own
Native Scheduler (`gdb.schedule`, also not part of Neo4j GDS; see
the [scheduling guide](../gds/scheduling.md)).
Personalised PageRank, native projection estimates, budget checks and cooperative
cancellation are implemented. FastRP/PageRank accept opt-in parallel execution;
default concurrency is 1. Other algorithms remain serial, and KNN accepts only 1.
See [algorithm modes](../gds/algorithms.md) and [resource controls](../gds/resources.md).

No persistent graph catalogue, Cypher projections, ML pipelines, model catalogue
or remote named-job cancellation. Unsupported configuration keys raise errors.
Seeds and community IDs are implementation-specific; compare documented semantics
and partitions. Results, including `.stream`, are materialised in the query result.

APOC includes scalar functions, traversal, exact metadata scans, dynamic
create/merge, mergeNodes and selected JSON/Cypher interchange. It has no plugin
loader, periodic background jobs, general refactor suite or JSONPath. Files and
plain HTTP are supported import sources; HTTPS is not. File export effects are
not rolled back with graph mutations. See [APOC](../apoc/README.md) and
[imports](../imports/README.md).

## Transactions and scale

Read statements run concurrently and, from version 1.6.1, read the last
committed state without waiting for an open writer; read transactions get a
repeatable-read snapshot at `BEGIN` ([snapshot reads](../operations/transactions.md#snapshot-reads)).
Write execution is exclusive: there is no concurrent write execution yet. Group commit shares syncs between concurrent clients; it does not
parallelise mutation execution. See [transactions](../operations/transactions.md).

Hybrid mode bounds decoded base-property caching, while topology, adjacency,
property locations and derived indexes remain in RAM. This is not a fully paged
database. Hybrid checkpoints incrementally compact stale values, but structural
history remains until a logical dump/restore. Resident checkpoints write the
whole graph. One process must own each durable directory; the built-in duplicate
open guard covers handles in one process, not other OS processes.

## Protocol and administration

The server speaks Bolt 4.4 and 5.0–5.4 with a single-node routing table, not a
replicated cluster. Read-only [replica databases](../operations/replicas.md) on
the same instance are addressed by database name; drivers are not routed to them. The native 0.1 drivers negotiate 4.4 and use direct connections; they do
not implement routing, pooling, managed retries or lazy cursors. They buffer
records and support explicit transactions and native type mapping. See
[driver setup and limits](../integrations/bolt.md). Other clients negotiate the
newest version they share with the server. `dbms.procedures()` and
`dbms.functions()` return empty compatibility rows. `db.indexes()` and
`db.constraints()` list every index and constraint kind. Running statements can
be [listed, stopped and given time limits](../operations/transactions.md#time-limits).

Basic HELLO authentication is mandatory. Users, roles and whole-database grants
persist in the protected system database. System administration privileges are
separate; label and property restrictions remain deferred. Server passwords use Argon2id.
Native TLS is available once a certificate is configured; see
[encrypted connections](../operations/authentication.md#encrypted-connections).
Explorer connects remotely over Bolt.

## Related articles

[Documentation](../README.md) · [Drivers](../integrations/bolt.md)
