- 05 6月, 2023 1 次提交
-
-
由 Anton Klaren 提交于
-
- 02 6月, 2023 10 次提交
-
-
由 Louise Söderström 提交于
Also, some cleanup
-
由 Louise Söderström 提交于
-
由 Louise Söderström 提交于
Co-authored-by: NLove Kristofer Leifland <love.leifland@neotechnology.com>
-
由 Gustav Hedengran 提交于
Setting is deprecated and was removed in a523c195. However, setting must still exist with `@Deprecated` annotation for proper API documentation, and in order to show up in `SHOW SETTINGS`.
-
由 Therese Magnusson 提交于
-
由 Henrik Nyman 提交于
Fixes a race condition causing incorrect reporting of counts to the page cache tracer when closing a transaction, after running an embedded query with the parallel runtime and using the Core API on returned entities within a result transformer. The problem was that the ValueMapper used in ResultSubscriber was exposing the internal transaction directly to returned entities, which could lead to uses of ambient cursors updating non-threadsafe counts while execution contexts were merging their reports back to the transaction on query close. This is solved by providing the subscriber with an ExecutionContextValueMapper based on the execution context of the resources used for query intialization. These resources now have to be closed from the query calling thread after merging of worker execution contexts is completed.
-
由 MishaDemianenko 提交于
-
由 erik-leffler 提交于
-
由 Anders Månsson 提交于
.. to distinguish the case where the user has provided different type constraints for the same (label/type, property)-pair.
-
由 Anton Klarén 提交于
Collapse nested JSON objects in the query logger when `db.logs.query.annotation_data_as_json_enabled` setting is true Log4j's filter and `fluentd` do not handle nested JSON objects by default. This PR changes the behavior to collapse them with dots, e.g. ``` { "annotationData": { "type": "system", "source": "foo" } } ``` to ``` { "annotationData.type": "system", "annotationData.source": "foo" } ``` This will allow for smoother integration with existing tools without the need to resort to error-prone regex parsing of JSON. Fixes: #13090
-
- 01 6月, 2023 14 次提交
-
-
由 Arne Fischereit 提交于
For the 0-th repetition, the node patterns outside the QPP are bound to the same node and the predicates inside the QPP are not enforced.
-
由 Matthew Parnell 提交于
-
由 Tobias Johansson 提交于
-
由 Tobias Johansson 提交于
Uses the ServerPoliciesPlugin applied with the current RoutingContext when determining if execution should be local or remote. If remote, then we use the plugin again to form the routing table for the driver (meaning that routing context is now part of the key for cached driver instances).
-
由 Tobias Johansson 提交于
Return a rich result containing the internal bolt addresses and server ids.
-
由 Jonas Holgersson 提交于
-
由 erik-leffler 提交于
-
由 emmaholmbergohlsson 提交于
-
由 grant lodge 提交于
-
由 Therese Magnusson 提交于
Co-authored-by: NLasse Heemann <lasse.heemann@neo4j.com>
-
由 Louise Söderström 提交于
-
由 Louise Söderström 提交于
-
由 Louise Söderström 提交于
This way,there is no need to implement the runtime for the notIsTyped AST.
-
由 Louise Söderström 提交于
-
- 31 5月, 2023 13 次提交
-
-
由 Nils Ceberg 提交于
-
由 Lars Korduner 提交于
-
由 Petr Janouch 提交于
Graph selection was handled only by Query router/Fabric layer and USE clauses were stripped from queries there before queries were sent to Cypher stack. In order to simplify Query router, queries are sent to Cypher stack unmodified. Allowing USE clause in layers bellow Query router means that some checks must be performed there mainly because of queries submitted through Core API. Co-authored-by: NLinneaAndersson <linneamaria10@gmail.com>
-
由 Jonas Holgersson 提交于
-
由 Gustav Hedengran 提交于
-
由 Gustav Hedengran 提交于
Co-authored-by: NSatia Herfert <sherfert@users.noreply.github.com>
-
由 Gustav Hedengran 提交于
- Includes both test construction and production code construction Co-authored-by: NSatia Herfert <sherfert@users.noreply.github.com>
-
由 Gustav Hedengran 提交于
- For some test scenarios the expression rewriting wasn't happening before this change. - Also now ensures that rewriting _always_ happens after parsing an expression. Co-authored-by: NSatia Herfert <sherfert@users.noreply.github.com>
-
由 Gustav Hedengran 提交于
Co-authored-by: NSatia Herfert <sherfert@users.noreply.github.com>
-
由 emmaholmbergohlsson 提交于
New kernel version 5.9 connected to the type constraints Exposes type constraints on Core API Introduces property type constraints to restrict the type of node and/or relationship properties. Can be created with commands like: CREATE CONSTRAINT nodePropertyStringType FOR (n:Label) REQUIRE n.prop IS :: STRING or CREATE CONSTRAINT relPropertyBooleanType FOR ()-[r:REL_TYPE]-() REQUIRE r.prop IS :: BOOLEAN
-
由 Valdemar Roxling 提交于
The degree store would not seek in "previous changes" correctly, which could result in incorrect reported degrees during checkpoint which in turn could result in count store corruption
-
由 Louise Söderström 提交于
The precedence for IS NULL and IS NOT NULL were broken by mistake while adding the GQL IS keyword. This commit disallows the labels NOT, NULL and TYPED for label expressions with the IS keyword and unescaped labels. Co-authored-by: NNadja Müller <nadja.muller@neotechnology.com>
-
由 MishaDemianenko 提交于
-
- 30 5月, 2023 2 次提交
-
-
由 Anders Månsson 提交于
-
由 Mattias Finné 提交于
-