Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Values created with datetime() panics with "wrong value marker" (support for ZonedDateTime missing?) #63

Open
magnusart opened this issue Nov 23, 2024 · 2 comments

Comments

@magnusart
Copy link

When I use the datetime() function in a Cypher Create query I see the value below in Memgraph lab.

{
   "year": 2024,
   "month": 11,
   "day": 23,
   "hour": 22,
   "minute": 40,
   "second": 32,
   "nanosecond": 960870000,
   "timeZoneOffsetSeconds": 0,
   "timeZoneId": "Etc/UTC"
}

But when I try with rsmgclient I get the error "wrong value marker" from the client. I previously used localdatetime() function and that worked fine. But it is missing the timezone.

Could this be because support for ZonedDateTime is missing from the client?

pub enum Value {

It was released before summer as far as I can see
https://memgraph.com/docs/release-notes#memgraph-v2170---may-22-2024

@antejavor
Copy link

Hi, @magnusart, thanks for reporting this 🙇‍♂️ . Yeah, the client didn't catch up with the changes in Memgraph.

Keep tracking the issue until we update this.

Is this a big blocker for you currently?

@DiscordJim
Copy link

DiscordJim commented Dec 8, 2024

This is a big blocker on my end, can confirm I am dealing with it on all nodes with attached dates.

@gitbuda gitbuda moved this to Todo in drivers Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

3 participants