new
improved
AuraDB Enterprise
AuraDB Professional
AuraDB Free
AuraDS Self-Start
AuraDS Enterprise
Neo4j Aura Database feature update!
The following core Neo4j Database features are now available for users in Aura:
- Anonymous usage data reporting: Neo4j sends a small amount of anonymous usage data back to Neo4j. This helps us understand how our products are used and improve them. The reporting can be disabled with the configuration setting dbms.usage_report.enabled=false. For a full description of the reported data, please refer to the Anonymous usage data report documentation page.
- Add a new deprecatedBy column to SHOW PROCEDURES and SHOW FUNCTION to show if a procedure/function has a replacement when it has been deprecated.
- It is now possible to reference variables from within a Quantified Path Pattern (QPP) that are not defined directly insidethe QPP. For example:
MATCH (x)
MATCH ((a)--(b) WHERE a.h >x.h)*(s)-->(u)
RETURN *
To use x as a predicate, it is no longer necessary for it to have been previously defined; so this query can now be rewritten as:
MATCH (x)-->(y)((a)-[e]->(b) WHERE a.h > x.h)*
RETURN *
- To further comply with the GQL specification, we have extended the existing trim(), ltrim() and rtrim() functions to optionally allow the specification of which characters to trim, as well as the addition of a btrim() function which trims both ends of a string. For example, RETURN BTRIM('xyzzyNeo4jzyx', 'xyz') returns ‘Neo4j’. For details, please refer to the String function - Cypher manual.
- Deprecate property references that depend on the order of evaluationwithin a MERGE clause, for example:
MERGE (a {prop:'p'})-[:T]->(b {prop:a.prop}).
The following is still allowed:
MATCH (a {prop:'p'})
MERGE (b {prop:a.prop}).
- Existing trim(), ltrim() and rtrim() functions optionally allow the specification of which characters to trim, whilst a new btrim() function which trims both ends of a string.
- It is now possible to reference elements from within a Quantified Path Pattern that are not directly adjacent to the QPP.
We hope you enjoy these new capabilities, please refer to the Neo4j changelog for full details of the changes.