TuringDB home pagelight logodark logo
  • Discord
  • GitHub
  • Website
TuringDB

Get Started

  • Introduction
  • Get Started
  • Claude Code Skill
  • Commands

Concepts

  • Overview
  • A Columnar Graph Database
  • Versioning System
  • The DataPart System
  • Zero-Locking Architecture
  • Snapshots Isolation

Benchmarks

  • Results Summary
  • Technical Report

Query Language

  • Overview
  • Matching
  • Paths
  • Results and Aggregation
  • Subqueries
  • Functions and Types
  • Writing Data
  • Procedures and Commands
  • CheatSheet

Importing data

  • JSONL
  • CSV
  • Neo4j
  • GML
  • Parquet

Graph Development

  • Create Graph
  • Load Graph
  • Load External data
  • Create a Change
  • List Changes
  • Create Nodes and Edges
  • Update Properties
  • Submit a Change
  • Time Travel
  • Graph Examples

Vector Search

  • Vector Search

Graph Algorithms

  • Shortest Path

Tutorials

  • Example Notebooks

Python SDK

  • Get Started
  • Reference

Troubleshooting

  • Troubleshooting
Graph Development

Submit Change

Submit changes done to the database (just like a commit being submited in git)

  • Cypher
  • Python SDK
// Submit changes done to the database
CHANGE SUBMIT

// Checkout to main branch
checkout
# Submit changes done to the database
client.query("CHANGE SUBMIT")

# Checkout to main branch
client.checkout()

CHANGE SUBMIT commits any pending writes itself, so a COMMIT right before it is optional. In the Python SDK, call client.checkout() afterwards to return to main: the client points at the submitted change until you do.

If two changes edit the same node, the second submit reports a conflict, for example This change attempted to update Node 0 (...) which has been modified on main. The failed change stays open: fix it and submit again, or discard it with CHANGE DELETE. See Writing data.

Update PropertiesTime Travel
githublinkedinyoutubediscord