Tags · MostUsing/memgraph · GitHub
Skip to content

Tags: MostUsing/memgraph

Tags

v3.7.2

Toggle v3.7.2's commit message
Set override version

v3.7.2-rc1

Toggle v3.7.2-rc1's commit message
Set override version

v3.7.1

Toggle v3.7.1's commit message
fix string

v3.7.1-rc1

Toggle v3.7.1-rc1's commit message
Update CMakeLists.txt with new memgraph override version [skip tests]…

… [skip build]

v3.7.0

Toggle v3.7.0's commit message
Fix RPM aarch64 release

v3.7.0-rc2

Toggle v3.7.0-rc2's commit message
Merge branch 'master' into release/3.7

v3.7.0-rc1

Toggle v3.7.0-rc1's commit message
fix docker artifacts

v3.6.2

Toggle v3.6.2's commit message
Set override version to 3.6.2

v3.6.2-rc1

Toggle v3.6.2-rc1's commit message
Set override version to 3.6.2

v3.6.1

Toggle v3.6.1's commit message
Return current clock time when calling `datetime` with just timezone (m…

…emgraph#3339)

When calling `datetime()` with only a timezone field in the given map:

```cypher
RETURN datetime({timezone:"Europe/Brussels"});
```

this returned a `datetime` with the minimum value for all numeric
fields, such as year, month, day, hour, etc:

```
0000-01-01T00:00:00+00[Europe/Brussels]
```

The expected behaviour is that when *only* a timezone is given,
`datetime` should compute the current clock time in the given timezone.
This PR implements the correct (i.e., same as Neo4j) behaviour, but also
breaks the previous `datetime()` result if anyone was relying on that
specific behaviour.

The same query will now return something like:

```
2025-10-13 11:20:28.174118000[Europe/Brussels]
```