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

Setting parameters in the browser coerces NULL to string #1934

Open
thordal-indykite opened this issue Sep 7, 2023 · 1 comment
Open

Setting parameters in the browser coerces NULL to string #1934

thordal-indykite opened this issue Sep 7, 2023 · 1 comment

Comments

@thordal-indykite
Copy link

thordal-indykite commented Sep 7, 2023

Description

Browser interprets NULL as a string when setting parameters, but Cypher handles NULL as null

Reproduce Steps

Run

:params {
  foo: NULL
}

foo is now set to the string "NULL"

Expected Behavior

NULL and null are equivalent

Your Environment

Neo4j Browser version: 5.9.0

@OskarDamkjaer
Copy link
Contributor

Hi! We do support properly inferred parameter values when the => syntax is used. You can set get a null parameter like so :param foo => null. We're aware it's confusing that the different syntaxes work differently under the hood and have fixed it in Neo4j Workspace, but it's not made its way back to Neo4j Browser yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants