Question 1

Is Liquigraph still supported or maintained?

Accepted Answer

Liquigraph is being phased out in favor of the Neo4j plugin for Liquibase. While the 4.x branch has CI builds, active development has shifted, and users are encouraged to migrate for long-term stability.

Question 2

How do I integrate Liquigraph with Gradle?

Accepted Answer

You can add the Liquigraph plugin to your build.gradle file using the provided dependencies. Check the Liquigraph website or GitHub repository for specific configuration examples and version compatibility.

Question 3

What's better for Neo4j, Liquigraph or Liquibase?

Accepted Answer

Liquigraph offers a simpler, Cypher-native approach but is being deprecated. Liquibase's Neo4j plugin provides a more feature-rich, ecosystem-supported alternative with broader database compatibility and active development.

Question 4

How can I rollback a migration in Liquigraph?

Accepted Answer

Liquigraph supports rollback by defining optional rollback scripts in Cypher when creating migrations. You need to write the reverse logic explicitly to enable this feature during deployment.

Question 5

Can I use Liquigraph with Neo4j 3.x?

Accepted Answer

Yes, but you must use the 3.x branch of Liquigraph, as specified in the README. However, due to the project's deprecation, consider switching to Liquibase for future-proofing.

Question 6

How to run a dry run with Liquigraph CLI?

Accepted Answer

Use the dry run option available in the CLI commands to simulate migrations without applying changes. This helps verify Cypher scripts and prevent unintended database modifications.

Liquigraph

What is Liquigraph?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions