How to update information in an existing node instead of creating a new one using Dgraph?
up vote
1
down vote
favorite
I am writing a Golang application using Dgraph for persisting objects. From the documentation, I can infer that a new UID
and hence a new node is created everytime I mutate an object/run the code.
Is there a way to update the same node data instead for creating a new node?
I tried changing the UID
to use "_:name"
for the UID
field but even this creates a new node everytime the application is run. I wish to be able to update the existing node if it is already present in the DB instead of creating a new node for it.
dgraph dgraph-dgo
add a comment |
up vote
1
down vote
favorite
I am writing a Golang application using Dgraph for persisting objects. From the documentation, I can infer that a new UID
and hence a new node is created everytime I mutate an object/run the code.
Is there a way to update the same node data instead for creating a new node?
I tried changing the UID
to use "_:name"
for the UID
field but even this creates a new node everytime the application is run. I wish to be able to update the existing node if it is already present in the DB instead of creating a new node for it.
dgraph dgraph-dgo
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am writing a Golang application using Dgraph for persisting objects. From the documentation, I can infer that a new UID
and hence a new node is created everytime I mutate an object/run the code.
Is there a way to update the same node data instead for creating a new node?
I tried changing the UID
to use "_:name"
for the UID
field but even this creates a new node everytime the application is run. I wish to be able to update the existing node if it is already present in the DB instead of creating a new node for it.
dgraph dgraph-dgo
I am writing a Golang application using Dgraph for persisting objects. From the documentation, I can infer that a new UID
and hence a new node is created everytime I mutate an object/run the code.
Is there a way to update the same node data instead for creating a new node?
I tried changing the UID
to use "_:name"
for the UID
field but even this creates a new node everytime the application is run. I wish to be able to update the existing node if it is already present in the DB instead of creating a new node for it.
dgraph dgraph-dgo
dgraph dgraph-dgo
asked Oct 11 at 4:53
hemanik
155313
155313
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
Unfortunately the docs aren't very beginner friendly yet :/
To modify / mutate existing data you have to run a set
operation and supply a rdf-triple like <uid> <predicate> "value"
/ <objectYouWantToModify> <attributeYouWantToModify> "quotedStringValue"
. If it is not an attribute but an edge, the value has to be another <uid>
.
The full mutation would be for example
{
set {
<0x2> <name> "modified-name" .
}
}
The .
terminates the sequence and there is an optional fourth parameter you can use to also assign a label
.
Check https://www.w3.org/TR/n-quads/ for further details.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Unfortunately the docs aren't very beginner friendly yet :/
To modify / mutate existing data you have to run a set
operation and supply a rdf-triple like <uid> <predicate> "value"
/ <objectYouWantToModify> <attributeYouWantToModify> "quotedStringValue"
. If it is not an attribute but an edge, the value has to be another <uid>
.
The full mutation would be for example
{
set {
<0x2> <name> "modified-name" .
}
}
The .
terminates the sequence and there is an optional fourth parameter you can use to also assign a label
.
Check https://www.w3.org/TR/n-quads/ for further details.
add a comment |
up vote
2
down vote
Unfortunately the docs aren't very beginner friendly yet :/
To modify / mutate existing data you have to run a set
operation and supply a rdf-triple like <uid> <predicate> "value"
/ <objectYouWantToModify> <attributeYouWantToModify> "quotedStringValue"
. If it is not an attribute but an edge, the value has to be another <uid>
.
The full mutation would be for example
{
set {
<0x2> <name> "modified-name" .
}
}
The .
terminates the sequence and there is an optional fourth parameter you can use to also assign a label
.
Check https://www.w3.org/TR/n-quads/ for further details.
add a comment |
up vote
2
down vote
up vote
2
down vote
Unfortunately the docs aren't very beginner friendly yet :/
To modify / mutate existing data you have to run a set
operation and supply a rdf-triple like <uid> <predicate> "value"
/ <objectYouWantToModify> <attributeYouWantToModify> "quotedStringValue"
. If it is not an attribute but an edge, the value has to be another <uid>
.
The full mutation would be for example
{
set {
<0x2> <name> "modified-name" .
}
}
The .
terminates the sequence and there is an optional fourth parameter you can use to also assign a label
.
Check https://www.w3.org/TR/n-quads/ for further details.
Unfortunately the docs aren't very beginner friendly yet :/
To modify / mutate existing data you have to run a set
operation and supply a rdf-triple like <uid> <predicate> "value"
/ <objectYouWantToModify> <attributeYouWantToModify> "quotedStringValue"
. If it is not an attribute but an edge, the value has to be another <uid>
.
The full mutation would be for example
{
set {
<0x2> <name> "modified-name" .
}
}
The .
terminates the sequence and there is an optional fourth parameter you can use to also assign a label
.
Check https://www.w3.org/TR/n-quads/ for further details.
answered Nov 11 at 8:24
TommyF
1,0651726
1,0651726
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52752468%2fhow-to-update-information-in-an-existing-node-instead-of-creating-a-new-one-usin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown