Repository navigation
Memgraph v3.14.0 - #1764
Merged
Merged
Memgraph v3.14.0#1764
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
vpavicic
marked this pull request as draft
September 15, 2026 12:50
) * docs: the bare pattern shorthand takes what a MATCH pattern takes The page stated two rules that no longer hold: that the shorthand's pattern cannot introduce names of its own, and that it holds a pattern and nothing else so a filter needs the `MATCH` form. It now takes a variable it declares itself, a trailing `WHERE`, a comma-separated list, a named path and a lone node. The worked example is the filter the old text used to send to the `MATCH` form, written as the shorthand, with output from the page's own dataset. `COLLECT` still has no shorthand. * docs: a pattern holding only a bound variable matches on its value A pattern that names a variable the query has already bound used to be ignored, so the row passed through whatever the variable held. It is now matched: a node is kept, a null matches nothing and drops the row, and a value that is neither raises. This applies to a top-level MATCH and a CALL {} subquery as well as to a subquery expression body, which the pages did not say. Also documents the rule that came with it: a pattern name inside a subquery expression body may not repeat a name from outside the body. Every output block was produced by running the query against its own page's dataset block.
* docs(querying): document the nullIf built-in nullIf(value1, value2) answers null where the two arguments are equal and the first argument otherwise, so it takes a value away where coalesce supplies one. * docs(querying): drop nullIf from the unsupported function list It was the only entry under the scalar functions heading, so the heading goes with it.
Co-authored-by: Cursor <cursoragent@cursor.com>
…1792) Document memgraph/memgraph#4962: on a coordinator, any Bolt scheme not listed in --auth-module-mappings now takes the same passthrough path as basic/none instead of being rejected outright. Describe the two-path rule, the per-scheme denial messages once SSO is configured, and the 3.13 -> 3.14 behavior change.
Documents the new instance-level disk_available row added in memgraph/memgraph#4952. Adds it to the SHOW STORAGE INFO reference table and the example output. Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com>
* docs: label expressions in node patterns and expressions * Update pages/querying/differences-in-cypher-implementations.mdx --------- Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com>
`OPTIONAL CALL ( scope ) { body }` keeps an input row whose subquery returns no
rows, with the subquery's columns set to null - the OPTIONAL MATCH contract.
Section 2.4 said the scoped `CALL (...)` form could not be combined with
`OPTIONAL` and showed the exact query that now works. It is replaced by 1.7
under the supported uses, and 2.4 now covers the case that is still rejected:
`OPTIONAL` on a procedure call rather than on a subquery, with the subquery
wrapping that does work.
Fill in the remaining breaking, feature, fix, and improvement notes for merged memgraph PRs on this release. Co-authored-by: Cursor <cursoragent@cursor.com>
2 tasks done
andrejtonev
reviewed
Oct 7, 2026
andrejtonev
left a comment
andrejtonev
left a comment
Contributor
There was a problem hiding this comment.
Comments on the 3.14 entries for the session and DROP DATABASE PRs (#4577, #4571, #4843, #4969). I checked each one against current master, on a live instance. One sentence in the #4577 entry is wrong, and two entries are missing.
Comment on lines
+114
to
+115
| that session's database. `SESSIONS` is a reserved keyword; quote it as a | ||
| bare identifier. |
Contributor
There was a problem hiding this comment.
SESSIONS isn't a reserved keyword. It works unquoted as a label, property, variable or relationship type (e.g. CREATE (n:SESSIONS {sessions: 1}), WITH 1 AS sessions RETURN sessions), so this sentence asks users to do something they don't need to. The same fix is suggested on the transactions page in #1814.
Suggested change
| that session's database. `SESSIONS` is a reserved keyword; quote it as a | |
| bare identifier. | |
| that session's database. |
… wording. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…nned (#1831) * docs: forced DROP DATABASE closes idle sessions on the dropped database * Apply batched suggestions from code review Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com> * Apply batched suggestions from code review Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com> --------- Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com> Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com>
* Document comparisons with null in lists and maps (memgraph#4794) * Document ordering comparisons for values without an order * Fix the ORDER BY sentence: two maps raise an error * Document which values a uniqueness constraint never treats as duplicates * Document ORDER BY and min/max over columns of different types (3.14 comparison series) * Keep only what readers hit; don't restate openCypher's comparison rules
* docs: explain and raise the open files limit (LimitNOFILE, Docker ulimit) * docs: soften open files sizing numbers and document the fs.nr_open ceiling Review follow-up: sizing figures are now approximate, and the section notes that LimitNOFILE cannot exceed fs.nr_open and how to check it. The heading anchor #handle-numerous-open-files-simultaneously is referenced from the Memgraph startup warning. * docs: pin open files limit change to v3.15 and trim unverified sizing numbers * docs: restore upstream heading ids after rebase, add ids to new steps, target v3.14 * docs: open files limit — only the hard limit matters on 3.14; symptoms, warning and INFO line
Auth queries can now run in an explicit transaction and apply together or not at all. Add a section on this to the authentication overview, and update the pages that said auth queries can't run in a transaction. Document that user and tenant profile changes are now refused in explicit transactions.
…eign-read UAF fix + precise stuck-drain diagnostics (#1843) * docs: database columns in SHOW ACTIVE USERS INFO and SHOW TRANSACTIONS outputs * docs(server-stats): login timestamp, username and database cells match the 3.14 behaviour
…#5129 #5132 #5135 (#1845)
* docs: SHOW SESSIONS and TERMINATE SESSIONS Documents the session management queries from memgraph/memgraph#4577: listing open Bolt sessions and terminating them from another connection, who can see and terminate which sessions, the result columns, and the SESSIONS reserved keyword. Adds both queries to the query privileges table. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: apply review on SHOW/TERMINATE SESSIONS Also fix the TERMINATE TRANSACTIONS parameter claim and add the database column of SHOW TRANSACTIONS. * docs: apply review on session wording and termination behavior * docs: real SHOW TRANSACTIONS output, FORCE note, pooled clients * Apply batched suggestions from code review Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com> Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com>
…1813) * docs: add conditional CALL subqueries with WHEN * docs: allow WHEN branches in EXISTS, COUNT and COLLECT bodies * docs: drop the predicate evaluation details * docs: use Croatian names in the conditional CALL example
…39 #5156 Co-authored-by: Cursor <cursoragent@cursor.com>
* update docs for FIPS builds of Memgraph * update docker page
vpavicic
marked this pull request as ready for review
October 21, 2026 11:09
memgraph#4985 moved to the 3.15 milestone.
…n targeted the database
katarinasupe
self-requested a review
October 21, 2026 12:00
katarinasupe
approved these changes
Oct 21, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make sure to do:
Milestones
Docs Integration Tracking
Breaking changes PRs
Docs needed (Memgraph PR → Docs PR)
Changelog (all PRs requiring a changelog entry)
UUIDlabel on default DB gauges when a data instance joins a cluster memgraph#4275 @colinbarrydatabaselabel when a database is renamed memgraph#5006 @colinbarry