Memgraph 3.1

next-env.d.ts

@@ -2,4 +2,4 @@
 /// <reference types="next/image-types/global" />
 
 // NOTE: This file should not be edited
-// see https://nextjs.org/docs/pages/api-reference/config/typescript for more information.
+// see https://nextjs.org/docs/basic-features/typescript for more information.

pages/advanced-algorithms/available-algorithms/community_detection.mdx

@@ -78,6 +78,8 @@ the procedure.
   gain in modularity goes below this threshold, a final iteration is performed using the
   `community_alg_threshold` value.
   Valid values are between 0 and 1 (exclusive). This parameter's value should be higher than `community_alg_threshold`.
+- `num_of_threads: integer (default=Half of the system's maximum thread count)` ➡ Specifies the number of threads used for parallel execution in the algorithm's parallelized parts. 
+**Note**: OpenMP (omp) is used for parallelization, so the actual thread usage may depend on system settings and OpenMP configurations.
 
 {<h4 className="custom-header"> Output: </h4>}
 

pages/advanced-algorithms/available-algorithms/date.mdx

@@ -1,6 +1,6 @@
 ---
 title: date
-description: Discover how to effectively perform date-based operations in your graph data with Memgraph's Date class. Also, check out our documentation to learn how to manipulate and better contextualize dates in your data. 
+description: Discover how to effectively perform date-based operations in your graph data with Memgraph's Date class. Also, check out our documentation to learn how to manipulate and better contextualize dates in your data.
 ---
 
 import { Steps } from 'nextra/components'
@@ -60,6 +60,18 @@ The `timezone` parameter can be specified with the database TZ identifier (text)
 name, as listed for
 [timezones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
 
+<Callout type="warning">
+
+Starting with `tzdata` version `2024b`, its format has changed and an
+incompatibility with the current libstdc++ has been introduced. As a result,
+using `tzdata` version `2024b` or later will break the timezone feature in
+Memgraph. This could lead to incorrect handling of timezones and unexpected
+behavior in your application. To avoid compatibility issues, please ensure that
+you are using `tzdata` `v2024a` or earlier with Memgraph until libstdc++ has
+been updated to support the new format in tzdata.
+
+</Callout>
+
 {<h4 className="custom-header"> Output: </h4>}
 
 - `formatted: string` ➡ The received time in the specified format.
@@ -69,7 +81,7 @@ name, as listed for
 Use the following query to get a string representation from a time value:
 
 ```cypher
-CALL date.format(74976, "h", "%Y/%m/%d %H:%M:%S %Z", "Mexico/BajaNorte") 
+CALL date.format(74976, "h", "%Y/%m/%d %H:%M:%S %Z", "Mexico/BajaNorte")
 YIELD formatted RETURN formatted;
 ```
 
@@ -107,6 +119,18 @@ The `timezone` parameter can be specified with the database TZ identifier (text)
 name, as listed for
 [timezones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
 
+<Callout type="warning">
+
+Starting with `tzdata` version `2024b`, its format has changed and an
+incompatibility with the current libstdc++ has been introduced. As a result,
+using `tzdata` version `2024b` or later will break the timezone feature in
+Memgraph. This could lead to incorrect handling of timezones and unexpected
+behavior in your application. To avoid compatibility issues, please ensure that
+you are using `tzdata` `v2024a` or earlier with Memgraph until libstdc++ has
+been updated to support the new format in tzdata.
+
+</Callout>
+
 {<h4 className="custom-header"> Output: </h4>}
 
 - `parsed: int` ➡ The number of time units that have elapsed since the Unix epoch.
@@ -116,7 +140,7 @@ name, as listed for
 Use the following query to parse the date string:
 
 ```cypher
-CALL date.parse("2023/08/03 14:30:00", "h", "%Y/%m/%d %H:%M:%S", "Europe/Zagreb") 
+CALL date.parse("2023/08/03 14:30:00", "h", "%Y/%m/%d %H:%M:%S", "Europe/Zagreb")
 YIELD parsed RETURN parsed;
 ```
 
@@ -134,9 +158,9 @@ Adds two numeric values representing quantities of time in specific units.
 
 {<h4 className="custom-header"> Input: </h4>}
 
-- `time: int` ➡ The first term in the addition operation. 
+- `time: int` ➡ The first term in the addition operation.
 - `unit: string` ➡ The time unit of the above value.
-- `add_value: int` ➡ The second term in the addition operation. 
+- `add_value: int` ➡ The second term in the addition operation.
 - `add_unit: string` ➡ The time unit of the above value.
 
 The `unit` parameter supports the following values: