-
Notifications
You must be signed in to change notification settings - Fork 418
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
SET on MERGE not storing edge properties inside the database on creation #1907
Comments
@tvaeyens I was able to reproduce your error -
|
This issue is stale because it has been open 60 days with no activity. Remove "Abondoned" label or comment or this will be closed in 14 days. |
@tvaeyens Looking into this |
I could have sworn that we fixed this bug a while ago. Sigh,... here it is with just a simple merge command.
|
@jrgemignani Thank you! |
@tvaeyens The fix is now in the master branch. I have submitted PRs to apply the fix to all of the lower branches. These are currently in review. |
@jrgemignani I tried it again with the latest version of the master branch, I can confirm that this issue has been resolved! Thank you! |
Describe the bug
When using a MERGE for a relation between two nodes that is not present in the database, the properties are not stored inside the database.
How are you accessing AGE (Command line, driver, etc.)?
What data setup do we need to do?
What is the necessary configuration info needed?
N/A
What is the command that caused the error?
This gives the following output which is correct:
When executing the next query:
This following output is received:
As you can see, the edge properties are not here anymore. Is this expected behavior? Or does this type of queries need to be formed in another way?
When looking inside the postgres database tables, the properties are also not there
Expected behavior
I thought the edge properties would still be present when executing the last query.
Environment (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: